← previous blocknext block →recent activity
Analyzing
Block #94,808,916
18 transactions · 18 stateful · 2026-08-10 15:17:51 UTC
Parallelism
61/100
Blocked
50%
Avg conflicts / tx
1.56
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #94,808,916 · 18 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w25w36w49w410w516w517w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0a57a2b8…3cdd
0x34b655…2a6f
14 touches
21 conflicts
0x0725ad1d…a03f
0x34b655…2a6f
8 touches
6 conflicts
0x7bcd679c…954d
0x34b655…2a6f
6 touches
3 conflicts
0xf2f4727d…cdb7
0x34b655…2a6f
6 touches
3 conflicts
0x54fb82e4…156a
0x34b655…2a6f
6 touches
3 conflicts
0xa279b18d…63bc
0x34b655…2a6f
4 touches
1 conflict
0xa3c36de0…3cf3
0x34b655…2a6f
4 touches
1 conflict
0xad95efd9…b4cf
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
21 conflicts on slot 0x0a57a2b8cd…773cdd
Audit this contract →
← previous block·next block →recent activity