← previous blocknext block →recent activity
Analyzing
Block #95,393,710
23 transactions · 21 stateful · 2026-08-12 16:32:51 UTC
Parallelism
83/100
Blocked
33%
Avg conflicts / tx
0.48
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #95,393,710 · 23 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w18w011w013w014w115w216w317w118w119w020w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf79df061…e005
0xe52b14…7230
8 touches
6 conflicts
0x51232c8c…f30c
0xe52b14…7230
6 touches
3 conflicts
0x51232c8c…f30e
0xe52b14…7230
6 touches
3 conflicts
0x5230ea1f…b878
0xe52b14…7230
6 touches
3 conflicts
0x5230ea1f…b87a
0xe52b14…7230
6 touches
3 conflicts
0xca2729d9…c9fa
0xe52b14…7230
4 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6426
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: 0xe52b1424…bb7230
6 conflicts on slot 0xf79df061c7…91e005
Audit this contract →
← previous block·next block →recent activity