← previous blocknext block →recent activity
Analyzing
Block #96,609,453
14 transactions · 12 stateful · 2026-08-16 22:30:25 UTC
Parallelism
71/100
Blocked
25%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #96,609,453 · 14 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
1w02w13w24w013w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2d651956…12e8
0x34b655…2a6f
8 touches
6 conflicts
0xb3fb9fb5…64db
0x34b655…2a6f
4 touches
1 conflict
0x34724223…fd0f
0x34b655…2a6f
4 touches
1 conflict
0x0e246445…9e0e
0x34b655…2a6f
4 touches
1 conflict
0x15c6cd62…05e7
0x34b655…2a6f
4 touches
1 conflict
0x37ce0b10…39b8
0x34b655…2a6f
2 touches
0 conflicts
0x3a3d2837…2516
0x34b655…2a6f
2 touches
0 conflicts
0x5d9e6c20…078c
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
6 conflicts on slot 0x2d65195682…4112e8
Audit this contract →
← previous block·next block →recent activity