← previous blocknext block →recent activity
Analyzing
Block #95,202,883
16 transactions · 15 stateful · 2026-08-12 00:20:18 UTC
Parallelism
69/100
Blocked
27%
Avg conflicts / tx
0.63
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #95,202,883 · 16 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
7w08w19w210w311w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x51232c8c…f30c
0xe52b14…7230
10 touches
10 conflicts
0x51232c8c…f30e
0xe52b14…7230
10 touches
10 conflicts
0xa6e37efb…afc0
0xe52b14…7230
10 touches
10 conflicts
0xa6e37efb…afc2
0xe52b14…7230
10 touches
10 conflicts
0xf79df061…e005
0xe52b14…7230
10 touches
10 conflicts
0x05b62a25…cd8c
0xe52b14…7230
9 touches
10 conflicts
0xa169711f…c7f3
0x34b655…2a6f
2 touches
0 conflicts
0xacd1b162…bee6
0x34b655…2a6f
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: 0xe52b1424…bb7230
10 conflicts on slot 0x51232c8c1f…6df30c
Audit this contract →
← previous block·next block →recent activity