← previous blocknext block →recent activity
Analyzing
Block #94,479,617
15 transactions · 14 stateful · 2026-08-09 11:40:05 UTC
Parallelism
47/100
Blocked
64%
Avg conflicts / tx
2.13
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #94,479,617 · 15 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
1w02w03w14w25w36w47w59w510w611w614w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x95c47f03…f1bb
0x34b655…2a6f
16 touches
28 conflicts
0xbb520828…94c0
0x34b655…2a6f
6 touches
3 conflicts
0x216a925b…4353
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x6284960e…adc8
0x34b655…2a6f
4 touches
1 conflict
0x9000d2ee…2a11
0x34b655…2a6f
4 touches
1 conflict
0xf2fc1fab…45e9
0x34b655…2a6f
4 touches
1 conflict
0x19d0eecc…6863
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 0x95c47f0322…51f1bb
Audit this contract →
← previous block·next block →recent activity