← previous blocknext block →recent activity
Analyzing
Block #96,209,353
14 transactions · 10 stateful · 2026-08-15 12:57:46 UTC
Parallelism
79/100
Blocked
30%
Avg conflicts / tx
0.21
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #96,209,353 · 14 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w06w18w210w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x394971b4…63d9
0x34b655…2a6f
4 touches
1 conflict
0xdf6c3e51…c493
0x34b655…2a6f
4 touches
1 conflict
0xf219f7cf…7379
0xa6afd3…d132
4 touches
1 conflict
0x9a3068dd…18f0
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xed854760…4f7d
0x34b655…2a6f
3 touches
1 conflict
0x75cde085…23d6
0xa6afd3…d132
3 touches
1 conflict
0xe2263bea…6aa0
0x2b46c0…1669
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 0x394971b4be…9a63d9
Audit this contract →
← previous block·next block →recent activity