← previous blocknext block →recent activity
Analyzing
Block #96,490,956
14 transactions · 13 stateful · 2026-08-16 12:34:07 UTC
Parallelism
57/100
Blocked
38%
Avg conflicts / tx
1.07
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #96,490,956 · 14 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w26w311w412w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x20fb35c7…09c2
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
8 touches
6 conflicts
0x6c8898de…8758
0x34b655…2a6f
6 touches
3 conflicts
0x5df7cf2b…bbe5
0x34b655…2a6f
4 touches
1 conflict
0x038b9243…553d
0x34b655…2a6f
4 touches
1 conflict
0xd66696e0…0842
0x34b655…2a6f
4 touches
1 conflict
0x7ce5b49a…237c
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
10 conflicts on slot 0x20fb35c73e…3b09c2
Audit this contract →
← previous block·next block →recent activity