← previous blocknext block →recent activity
Analyzing
Block #94,318,508
11 transactions · 11 stateful · 2026-08-08 22:01:42 UTC
Parallelism
55/100
Blocked
36%
Avg conflicts / tx
0.82
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #94,318,508 · 11 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w17w29w310w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa86351b8…2c5a
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xf6ff4f4a…e414
0x34b655…2a6f
4 touches
1 conflict
0xf7cf8182…7228
0x34b655…2a6f
4 touches
1 conflict
0x14b29ddb…0fd3
0x34b655…2a6f
4 touches
1 conflict
0x1caf0c05…15ce
0x34b655…2a6f
4 touches
1 conflict
0x26242d99…39ae
0x34b655…2a6f
4 touches
1 conflict
0x34d95d94…3a16
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
6 conflicts on slot 0xa86351b861…d52c5a
Audit this contract →
← previous block·next block →recent activity