← previous blocknext block →recent activity
Analyzing
Block #96,149,624
10 transactions · 8 stateful · 2026-08-15 07:57:22 UTC
Parallelism
60/100
Blocked
38%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #96,149,624 · 10 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
1w03w14w28w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0xfcfc2ae3…972b
0x34b655…2a6f
6 touches
3 conflicts
0x42b10c57…3ee7
0x34b655…2a6f
4 touches
1 conflict
0x713ba679…f953
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x23c53717…9436
0x34b655…2a6f
2 touches
0 conflicts
0x2b3c39da…774a
0x34b655…2a6f
2 touches
0 conflicts
0x41469894…598f
0x34b655…2a6f
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
3 conflicts on slot 0xbcbf5d09a8…c68bac
Audit this contract →
← previous block·next block →recent activity