← previous blocknext block →recent activity
Analyzing
Block #95,173,751
15 transactions · 14 stateful · 2026-08-11 21:53:47 UTC
Parallelism
87/100
Blocked
21%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #95,173,751 · 15 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w15w06w110w011w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6416b5d6…830e
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x002fed35…79fa
0x2a68ba…90c5
4 touches
1 conflict
0x7114f8b4…21f4
0x40c49f…2af0
3 touches
1 conflict
0xddc437c0…8078
0x34b655…2a6f
3 touches
1 conflict
0x9a54f439…de63
0x34b655…2a6f
2 touches
0 conflicts
0xa1fb92e0…d478
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: Perpl
1 conflict on slot 0x6416b5d6ed…2f830e
Audit this contract →
← previous block·next block →recent activity