← previous blocknext block →recent activity
Analyzing
Block #95,351,718
11 transactions · 11 stateful · 2026-08-12 13:00:10 UTC
Parallelism
73/100
Blocked
27%
Avg conflicts / tx
0.27
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #95,351,718 · 11 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
1w02w13w05w27w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf7640726…19a2
0x2a68ba…90c5
4 touches
1 conflict
0x3439dfbc…0d03
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0x992d3412…2cc3
0x851145…3f07
4 touches
1 conflict
0xa538600d…3da5
0x851145…3f07
4 touches
1 conflict
0x576d1ef2…f6a6
0x851145…3f07
3 touches
1 conflict
0x56a919c4…ab49
0x01bff4…1071
2 touches
0 conflicts
0x79aeeb89…03e8
0x01bff4…1071
2 touches
0 conflicts
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: Kuru Exchange: MarginAccount
1 conflict on slot 0xf764072638…5119a2
Audit this contract →
← previous block·next block →recent activity