← previous blocknext block →recent activity
Analyzing
Block #95,203,861
19 transactions · 18 stateful · 2026-08-12 00:25:13 UTC
Parallelism
68/100
Blocked
39%
Avg conflicts / tx
0.89
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #95,203,861 · 19 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
1w06w07w18w09w110w211w312w413w514w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x51232c8c…f30e
0xe52b14…7230
12 touches
15 conflicts
0x51232c8c…f30c
0xe52b14…7230
12 touches
15 conflicts
0xf79df061…e005
0xe52b14…7230
12 touches
15 conflicts
0xa6e37efb…afc2
0xe52b14…7230
12 touches
15 conflicts
0xa6e37efb…afc0
0xe52b14…7230
12 touches
15 conflicts
0x0c47a2f9…0332
0xe52b14…7230
11 touches
15 conflicts
0xa9419cb6…328f
0x40c49f…2af0
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
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: 0xe52b1424…bb7230
15 conflicts on slot 0x51232c8c1f…6df30e
Audit this contract →
← previous block·next block →recent activity