← previous blocknext block →recent activity
Analyzing
Block #95,072,738
18 transactions · 17 stateful · 2026-08-11 13:25:39 UTC
Parallelism
67/100
Blocked
47%
Avg conflicts / tx
1.11
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #95,072,738 · 18 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
2w03w16w07w29w010w111w212w313w414w515w016w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0008
0x0ea966…0742
12 touches
15 conflicts
0x724cd9ff…6684
0xe4f6e7…9657
12 touches
15 conflicts
0x44ad89ba…cf83
0xe4f6e7…9657
12 touches
15 conflicts
0x724cd9ff…6684
0x0cc9b2…7777
12 touches
15 conflicts
0xf3d10975…0d07
0x34b655…2a6f
6 touches
3 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
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: 0x0ea96615…ff0742
15 conflicts on slot 0x0000000000…000008
Audit this contract →
← previous block·next block →recent activity