← previous blocknext block →recent activity
Analyzing
Block #96,300,324
7 transactions · 7 stateful · 2026-08-15 20:35:20 UTC
Parallelism
71/100
Blocked
14%
Avg conflicts / tx
0.29
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #96,300,324 · 7 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w05w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd9b299ff…4367
0x34b655…2a6f
4 touches
1 conflict
0xf1d4a0e8…29f3
0x34b655…2a6f
4 touches
1 conflict
0x31b39922…1e65
0x34b655…2a6f
4 touches
1 conflict
0x31b39922…1e66
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x364026a6…1715
0x34b655…2a6f
2 touches
0 conflicts
0x424934c8…f2f1
0x34b655…2a6f
2 touches
0 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
1 conflict on slot 0xd9b299ff78…124367
Audit this contract →
← previous block·next block →recent activity