← previous blocknext block →recent activity
Analyzing
Block #96,046,091
13 transactions · 13 stateful · 2026-08-14 23:16:37 UTC
Parallelism
69/100
Blocked
46%
Avg conflicts / tx
0.69
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #96,046,091 · 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
2w03w14w05w16w27w29w312w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x68e81f14…d3c1
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x4c188934…158e
0x34b655…2a6f
6 touches
3 conflicts
0x3118505b…795e
0x34b655…2a6f
4 touches
1 conflict
0x410b84ab…1dbc
0x34b655…2a6f
4 touches
1 conflict
0x6280c6c6…11ac
0x34b655…2a6f
4 touches
1 conflict
0x6d1b72ee…6b78
0x34b655…2a6f
4 touches
1 conflict
0x96efe05d…5d48
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
3 conflicts on slot 0x68e81f1434…80d3c1
Audit this contract →
← previous block·next block →recent activity