← previous blocknext block →recent activity
Analyzing
Block #95,216,627
15 transactions · 15 stateful · 2026-08-12 01:29:26 UTC
Parallelism
67/100
Blocked
47%
Avg conflicts / tx
1.13
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #95,216,627 · 15 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w25w36w47w08w19w210w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x51232c8c…f30c
0xe52b14…7230
10 touches
10 conflicts
0xf91bbe5b…d918
0xe52b14…7230
10 touches
10 conflicts
0xf79df061…e005
0xe52b14…7230
10 touches
10 conflicts
0x0b0c2e8d…c1b8
0xe52b14…7230
10 touches
10 conflicts
0xa6e37efb…afc2
0xe52b14…7230
10 touches
10 conflicts
0xa6e37efb…afc0
0xe52b14…7230
10 touches
10 conflicts
0x6518075e…2b17
0x2a68ba…90c5
8 touches
6 conflicts
0x5b202df7…cdb2
0x40c49f…2af0
7 touches
6 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: 0xe52b1424…bb7230
10 conflicts on slot 0x51232c8c1f…6df30c
Audit this contract →
← previous block·next block →recent activity