← previous blocknext block →recent activity
Analyzing
Block #96,619,380
13 transactions · 11 stateful · 2026-08-16 23:20:20 UTC
Parallelism
62/100
Blocked
45%
Avg conflicts / tx
0.77
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #96,619,380 · 13 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w15w28w39w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbfd33a92…5c35
0x34b655…2a6f
8 touches
6 conflicts
0x784eaad2…d176
0x34b655…2a6f
8 touches
6 conflicts
0x1ee7ffe1…5b37
0x34b655…2a6f
7 touches
6 conflicts
0xa6176fff…d2c5
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…002f
0x1b6862…e19c
4 touches
1 conflict
0x6fd9ae7c…e984
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x00000000…00c9
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
6 conflicts on slot 0xbfd33a920c…0a5c35
Audit this contract →
← previous block·next block →recent activity