← previous blocknext block →recent activity
Analyzing
Block #96,274,306
24 transactions · 22 stateful · 2026-08-15 18:24:29 UTC
Parallelism
83/100
Blocked
23%
Avg conflicts / tx
0.54
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #96,274,306 · 24 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
4w05w17w010w011w216w317w218w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad0d
0x34b655…2a6f
8 touches
6 conflicts
0x91e8d927…3a11
0x34b655…2a6f
8 touches
6 conflicts
0x427dec7f…61c6
0x34b655…2a6f
8 touches
6 conflicts
0x7938c6fd…1cd1
0x34b655…2a6f
6 touches
3 conflicts
0xc3fc40da…1c60
0x34b655…2a6f
6 touches
3 conflicts
0xd0919e62…a2a8
0x34b655…2a6f
6 touches
3 conflicts
0x68297b76…8e24
0x34b655…2a6f
4 touches
1 conflict
0x74fd0a9b…3aaa
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 0x22e0cc1d4a…90ad0d
Audit this contract →
← previous block·next block →recent activity