← previous blocknext block →recent activity
Analyzing
Block #96,363,994
14 transactions · 10 stateful · 2026-08-16 01:55:33 UTC
Parallelism
71/100
Blocked
50%
Avg conflicts / tx
0.57
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #96,363,994 · 14 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w16w07w08w19w211w312w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2ad2e6d1…e192
0x34b655…2a6f
8 touches
6 conflicts
0x38badd90…a68c
0x34b655…2a6f
6 touches
3 conflicts
0x66bdb4c2…7ea6
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0xbb97db90…4c93
0xc8689a…ee79
4 touches
1 conflict
0x23a320fb…cbd7
0x34b655…2a6f
4 touches
1 conflict
0x329f2f7d…dcff
0x34b655…2a6f
4 touches
1 conflict
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
6 conflicts on slot 0x2ad2e6d1f9…35e192
Audit this contract →
← previous block·next block →recent activity