← previous blocknext block →recent activity
Analyzing
Block #96,315,969
16 transactions · 14 stateful · 2026-08-15 21:54:01 UTC
Parallelism
88/100
Blocked
7%
Avg conflicts / tx
0.19
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #96,315,969 · 16 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
2w05w06w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x29c1a140…099f
0x34b655…2a6f
4 touches
1 conflict
0x34a1ee7e…fb20
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0x1e04ad1e…c417
0x34b655…2a6f
4 touches
1 conflict
0x06e40499…165e
0x2b46c0…1669
2 touches
0 conflicts
0x02f5fbf9…5918
0x34b655…2a6f
2 touches
0 conflicts
0x08e8f2c9…a11a
0x34b655…2a6f
2 touches
0 conflicts
0x153d1e25…10ea
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 0x29c1a140f5…fc099f
Audit this contract →
← previous block·next block →recent activity