← previous blocknext block →recent activity
Analyzing
Block #96,527,609
13 transactions · 10 stateful · 2026-08-16 15:38:46 UTC
Parallelism
69/100
Blocked
30%
Avg conflicts / tx
0.46
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #96,527,609 · 13 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
5w06w07w18w09w010w212w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x34d95d94…3a16
0x34b655…2a6f
4 touches
1 conflict
0x7aad02c6…b979
0x34b655…2a6f
4 touches
1 conflict
0x1a5d321d…a474
0x34b655…2a6f
4 touches
1 conflict
0x9e70221e…171e
0x34b655…2a6f
4 touches
1 conflict
0xa4e9800f…4ab1
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0xd8834cf3…0004
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
1 conflict on slot 0x34d95d945c…603a16
Audit this contract →
← previous block·next block →recent activity