← previous blocknext block →recent activity
Analyzing
Block #93,926,623
20 transactions · 19 stateful · 2026-08-07 13:02:46 UTC
Parallelism
80/100
Blocked
37%
Avg conflicts / tx
0.65
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #93,926,623 · 20 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w05w18w011w212w114w015w116w217w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0000
0x116e7d…d8f1
8 touches
6 conflicts
0x00000000…0002
0x116e7d…d8f1
8 touches
6 conflicts
0x00000000…0003
0x116e7d…d8f1
8 touches
6 conflicts
0xb7143610…adc4
0x3bd359…433a
8 touches
6 conflicts
0xa472d565…9fe4
0x3bd359…433a
8 touches
6 conflicts
0x692a4122…76b8
0x350035…7777
8 touches
6 conflicts
0x44ad89ba…cf83
0x350035…7777
8 touches
6 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
What's blocking what?
Click any transaction in the timeline or graph to see which storage slots forced it to wait, and which later transactions it blocked.
The bottleneck
Throughput-killer: 0x116e7d07…d7d8f1
6 conflicts on slot 0x0000000000…000000
Audit this contract →
← previous block·next block →recent activity