← previous blocknext block →recent activity
Analyzing
Block #96,596,877
15 transactions · 11 stateful · 2026-08-16 21:27:10 UTC
Parallelism
80/100
Blocked
36%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #96,596,877 · 15 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w16w27w08w19w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xefeb7937…c283
0x34b655…2a6f
4 touches
1 conflict
0x28e5dbea…2f7f
0x34b655…2a6f
4 touches
1 conflict
0x2ffa0115…ed47
0x34b655…2a6f
4 touches
1 conflict
0x32915b25…6070
0x34b655…2a6f
4 touches
1 conflict
0x8faba3a7…8454
0x34b655…2a6f
4 touches
1 conflict
0x9a3463f0…0b73
0x34b655…2a6f
4 touches
1 conflict
0xa3c36de0…3cf3
0x34b655…2a6f
4 touches
1 conflict
0xb3fb9fb5…64db
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 0xefeb793761…25c283
Audit this contract →
← previous block·next block →recent activity