← previous blocknext block →recent activity
Analyzing
Block #96,113,303
14 transactions · 14 stateful · 2026-08-15 04:54:38 UTC
Parallelism
57/100
Blocked
36%
Avg conflicts / tx
0.5
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #96,113,303 · 14 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w07w18w211w312w413w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1c1b5ec9…43f6
0x34b655…2a6f
6 touches
3 conflicts
0x3b4d64bb…c98d
0x34b655…2a6f
6 touches
3 conflicts
0x454cdf57…aebc
0x34b655…2a6f
6 touches
3 conflicts
0xad2bb81f…4d6b
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x7604a8f8…d63a
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 0x1c1b5ec98b…8f43f6
Audit this contract →
← previous block·next block →recent activity