← previous blocknext block →recent activity
Analyzing
Block #95,214,992
16 transactions · 15 stateful · 2026-08-12 01:21:12 UTC
Parallelism
63/100
Blocked
33%
Avg conflicts / tx
0.94
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #95,214,992 · 16 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
6w07w18w29w310w411w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x51232c8c…f30c
0xe52b14…7230
12 touches
15 conflicts
0xa6e37efb…afc0
0xe52b14…7230
12 touches
15 conflicts
0xa6e37efb…afc2
0xe52b14…7230
12 touches
15 conflicts
0xf79df061…e005
0xe52b14…7230
12 touches
15 conflicts
0x0b0c2e8d…c1b8
0xe52b14…7230
12 touches
15 conflicts
0x60991f55…2987
0xe52b14…7230
11 touches
15 conflicts
0xb18a7027…4cc6
0x34b655…2a6f
2 touches
0 conflicts
0xb19c04c4…0b3e
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
15 conflicts on slot 0x51232c8c1f…6df30c
Audit this contract →
← previous block·next block →recent activity