← previous blocknext block →recent activity
Analyzing
Block #96,638,613
16 transactions · 14 stateful · 2026-08-17 00:57:04 UTC
Parallelism
75/100
Blocked
36%
Avg conflicts / tx
0.38
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #96,638,613 · 16 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
1w03w14w05w19w114w215w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6bdb9869…7558
0x34b655…2a6f
6 touches
3 conflicts
0x71604178…a3a8
0x34b655…2a6f
4 touches
1 conflict
0x76082747…e229
0x34b655…2a6f
4 touches
1 conflict
0xab96ac84…a512
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xd13ef842…4400
0x34b655…2a6f
4 touches
1 conflict
0x70959679…a310
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0002
0x103de0…bb55
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 0x6bdb9869c7…427558
Audit this contract →
← previous block·next block →recent activity