← previous blocknext block →recent activity
Analyzing
Block #96,356,908
6 transactions · 3 stateful · 2026-08-16 01:19:55 UTC
Parallelism
67/100
Blocked
33%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #96,356,908 · 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
4w05w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb8746edd…bc38
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xb88ff3f4…823a
0x34b655…2a6f
4 touches
1 conflict
0x06726618…fafd
0x34b655…2a6f
2 touches
0 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
2 touches
0 conflicts
0x326a02b5…8dad
0x34b655…2a6f
2 touches
0 conflicts
0x5b0edc1d…65d6
0x34b655…2a6f
2 touches
0 conflicts
0x6cba9fae…d9f5
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 0xb8746edd05…cebc38
Audit this contract →
← previous block·next block →recent activity