← previous blocknext block →recent activity
Analyzing
Block #96,555,047
8 transactions · 6 stateful · 2026-08-16 17:56:45 UTC
Parallelism
75/100
Blocked
17%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #96,555,047 · 8 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x261cbea7…e35d
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0x261cbea7…e35e
0x34b655…2a6f
4 touches
1 conflict
0x31d2cc98…b3c7
0x34b655…2a6f
4 touches
1 conflict
0x6d6c44e2…8f45
0x34b655…2a6f
3 touches
1 conflict
0xba078c04…9572
0x34b655…2a6f
3 touches
1 conflict
0x574628e9…dcc3
0x34b655…2a6f
2 touches
0 conflicts
0x628359b1…7263
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
1 conflict on slot 0x261cbea79d…12e35d
Audit this contract →
← previous block·next block →recent activity