← previous blocknext block →recent activity
Analyzing
Block #94,793,254
20 transactions · 19 stateful · 2026-08-10 13:59:03 UTC
Parallelism
80/100
Blocked
37%
Avg conflicts / tx
0.45
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #94,793,254 · 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
2w03w14w07w08w111w012w114w215w317w119w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5c677e67…7636
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x94bb14fe…8f47
0x34b655…2a6f
6 touches
3 conflicts
0x77efb543…f7c2
0x34b655…2a6f
4 touches
1 conflict
0x77efb543…f7c3
0x34b655…2a6f
4 touches
1 conflict
0x94f2c3b4…4ef6
0x34b655…2a6f
4 touches
1 conflict
0xb9c84c75…b267
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: Perpl
3 conflicts on slot 0x5c677e67f8…2f7636
Audit this contract →
← previous block·next block →recent activity