← previous blocknext block →recent activity
Analyzing
Block #95,216,879
18 transactions · 18 stateful · 2026-08-12 01:30:42 UTC
Parallelism
78/100
Blocked
33%
Avg conflicts / tx
0.67
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #95,216,879 · 18 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
1w02w13w08w09w110w211w313w014w115w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0b0c2e8d…c1b8
0xe52b14…7230
8 touches
6 conflicts
0xf79df061…e005
0xe52b14…7230
8 touches
6 conflicts
0xbde524f4…43bf
0x34b655…2a6f
6 touches
3 conflicts
0x217bd767…b79e
0x34b655…2a6f
6 touches
3 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0xf3d10975…0d07
0x34b655…2a6f
6 touches
3 conflicts
0x22e30c94…a508
0xe52b14…7230
6 touches
3 conflicts
0x51232c8c…f30c
0xe52b14…7230
6 touches
3 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
6 conflicts on slot 0x0b0c2e8d5e…dbc1b8
Audit this contract →
← previous block·next block →recent activity