← previous blocknext block →recent activity
Analyzing
Block #96,435,856
6 transactions · 5 stateful · 2026-08-16 07:56:58 UTC
Parallelism
67/100
Blocked
20%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #96,435,856 · 6 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
1w04w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x66bdb4c2…7ea6
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x2aab0897…78f7
0x34b655…2a6f
2 touches
0 conflicts
0x3ab86b5a…8290
0x34b655…2a6f
2 touches
0 conflicts
0x4abaedb1…65b9
0x34b655…2a6f
2 touches
0 conflicts
0x645bb256…e86f
0x34b655…2a6f
2 touches
0 conflicts
0x70be0d05…fc4e
0x34b655…2a6f
2 touches
0 conflicts
0x824b4c5c…a6d0
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