← previous blocknext block →recent activity
Analyzing
Block #94,279,543
18 transactions · 16 stateful · 2026-08-08 18:44:17 UTC
Parallelism
56/100
Blocked
63%
Avg conflicts / tx
2.17
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #94,279,543 · 18 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w04w15w26w310w411w113w214w516w617w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0a57a2b8…3cdd
0x34b655…2a6f
16 touches
28 conflicts
0x734ee320…caae
0x34b655…2a6f
10 touches
10 conflicts
0x70e3da66…674a
0x34b655…2a6f
6 touches
3 conflicts
0x21b13351…17ec
0x34b655…2a6f
6 touches
3 conflicts
0x317baac2…214e
0x34b655…2a6f
4 touches
1 conflict
0x3de86e79…4d3d
0x34b655…2a6f
4 touches
1 conflict
0x3f25409b…f92b
0x34b655…2a6f
4 touches
1 conflict
0x6d1b72ee…6b78
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
28 conflicts on slot 0x0a57a2b8cd…773cdd
Audit this contract →
← previous block·next block →recent activity