← previous blocknext block →recent activity
Analyzing
Block #96,700,314
13 transactions · 12 stateful · 2026-08-17 06:07:23 UTC
Parallelism
54/100
Blocked
42%
Avg conflicts / tx
0.69
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #96,700,314 · 13 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w26w37w410w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd0b32ce7…083e
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x6bfea08b…3e56
0x34b655…2a6f
4 touches
1 conflict
0x6f4e7625…aba5
0x34b655…2a6f
4 touches
1 conflict
0x7fd55c5f…1f35
0x34b655…2a6f
4 touches
1 conflict
0xfe069486…2c54
0x34b655…2a6f
4 touches
1 conflict
0x00000000…00c9
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
3 conflicts on slot 0xd0b32ce772…ea083e
Audit this contract →
← previous block·next block →recent activity