← previous blocknext block →recent activity
Analyzing
Block #96,268,473
18 transactions · 18 stateful · 2026-08-15 17:55:08 UTC
Parallelism
72/100
Blocked
33%
Avg conflicts / tx
0.78
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #96,268,473 · 18 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w06w17w28w19w011w312w416w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x16f2b4e1…e98b
0x34b655…2a6f
6 touches
3 conflicts
0xb3fb9fb5…64db
0x34b655…2a6f
6 touches
3 conflicts
0xea1b8c07…b969
0x34b655…2a6f
6 touches
3 conflicts
0x4acc6dca…a868
0x34b655…2a6f
4 touches
1 conflict
0x5a31af35…35a1
0x34b655…2a6f
4 touches
1 conflict
0x6254804c…a03b
0x34b655…2a6f
4 touches
1 conflict
0x784eaad2…d177
0x34b655…2a6f
4 touches
1 conflict
0x859fe39d…effa
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
3 conflicts on slot 0x16f2b4e165…c7e98b
Audit this contract →
← previous block·next block →recent activity