← previous blocknext block →recent activity
Analyzing
Block #96,213,012
7 transactions · 5 stateful · 2026-08-15 13:16:10 UTC
Parallelism
71/100
Blocked
20%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #96,213,012 · 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
4w05w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd5abc901…166d
0x34b655…2a6f
4 touches
1 conflict
0xd6255b52…69e7
0x34b655…2a6f
4 touches
1 conflict
0x224d6800…4508
0x34b655…2a6f
2 touches
0 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
2 touches
0 conflicts
0x2e9d65ac…2265
0x34b655…2a6f
2 touches
0 conflicts
0x2e9d65ac…2266
0x34b655…2a6f
2 touches
0 conflicts
0x48203298…65cb
0x34b655…2a6f
2 touches
0 conflicts
0x4c86d0e4…e2f1
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 0xd5abc9010e…93166d
Audit this contract →
← previous block·next block →recent activity