← previous blocknext block →recent activity
Analyzing
Block #94,467,139
22 transactions · 20 stateful · 2026-08-09 10:37:16 UTC
Parallelism
82/100
Blocked
45%
Avg conflicts / tx
0.91
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #94,467,139 · 22 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
4w05w06w17w28w39w010w111w012w213w014w115w116w220w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xeae24c…0be0
8 touches
6 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0x0778475b…bd75
0x2a68ba…90c5
6 touches
3 conflicts
0xa1087a5c…66c4
0x754704…b603
6 touches
3 conflicts
0x8fe5ad1d…f9b4
0x065c9d…c394
6 touches
3 conflicts
0xb4780ad3…88a6
0x065c9d…c394
5 touches
3 conflicts
0x9cddc7cb…4afc
0x065c9d…c394
5 touches
3 conflicts
0xa456140c…d076
0x34b655…2a6f
4 touches
1 conflict
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: 0xeae24c72…e30be0
6 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity