← previous blocknext block →recent activity
Analyzing
Block #94,301,567
24 transactions · 22 stateful · 2026-08-08 20:35:44 UTC
Parallelism
79/100
Blocked
45%
Avg conflicts / tx
1
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #94,301,567 · 24 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
1w02w14w05w06w17w08w19w210w311w413w221w222w323w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa86351b8…2c5a
0x34b655…2a6f
10 touches
10 conflicts
0x11b69a7e…334e
0xee8c0e…1242
10 touches
10 conflicts
0xa1087a5c…66c4
0x754704…b603
10 touches
10 conflicts
0x002fed35…79fa
0x2a68ba…90c5
6 touches
3 conflicts
0x4a5956ef…e226
0x34b655…2a6f
6 touches
3 conflicts
0x99479bc5…3a88
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
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
10 conflicts on slot 0xa86351b861…d52c5a
Audit this contract →
← previous block·next block →recent activity