← previous blocknext block →recent activity
Analyzing
Block #96,372,460
12 transactions · 11 stateful · 2026-08-16 02:38:09 UTC
Parallelism
50/100
Blocked
55%
Avg conflicts / tx
0.67
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #96,372,460 · 12 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
2w03w14w26w38w410w411w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfe449cf3…289f
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6426
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xeb5d53a1…ad5f
0x34b655…2a6f
4 touches
1 conflict
0x0313aedc…bfaf
0x34b655…2a6f
4 touches
1 conflict
0x0505bae8…b4fb
0x34b655…2a6f
4 touches
1 conflict
0x0d488000…3831
0x34b655…2a6f
4 touches
1 conflict
0x19e1da6e…4a72
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
1 conflict on slot 0xfe449cf3cc…14289f
Audit this contract →
← previous block·next block →recent activity