← previous blocknext block →recent activity
Analyzing
Block #96,124,524
13 transactions · 12 stateful · 2026-08-15 05:51:05 UTC
Parallelism
77/100
Blocked
33%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #96,124,524 · 13 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w06w07w111w112w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7b481037…3457
0x34b655…2a6f
6 touches
3 conflicts
0x7ea60711…6098
0x34b655…2a6f
6 touches
3 conflicts
0x11431f9d…42c5
0x34b655…2a6f
4 touches
1 conflict
0x20078f8c…18af
0x34b655…2a6f
4 touches
1 conflict
0x213a54fa…c85f
0x34b655…2a6f
4 touches
1 conflict
0x23777ec3…ce84
0x34b655…2a6f
4 touches
1 conflict
0x2524c14e…c3fc
0x34b655…2a6f
4 touches
1 conflict
0x2a148cc8…549c
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 0x7b481037fb…ca3457
Audit this contract →
← previous block·next block →recent activity