← previous blocknext block →recent activity
Analyzing
Block #96,255,650
7 transactions · 4 stateful · 2026-08-15 16:50:38 UTC
Parallelism
71/100
Blocked
25%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #96,255,650 · 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
0x66bdb4c2…7ea6
0x34b655…2a6f
4 touches
1 conflict
0x6a8d8180…0ae3
0x34b655…2a6f
4 touches
1 conflict
0x0eaa3f4e…2992
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x0eb3ab36…88ba
0x34b655…2a6f
2 touches
0 conflicts
0x15be757a…275e
0x34b655…2a6f
2 touches
0 conflicts
0x15be757a…275f
0x34b655…2a6f
2 touches
0 conflicts
0x29c691cc…fe9f
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 0x66bdb4c268…a97ea6
Audit this contract →
← previous block·next block →recent activity