← previous blocknext block →recent activity
Analyzing
Block #95,112,277
16 transactions · 14 stateful · 2026-08-11 16:44:35 UTC
Parallelism
88/100
Blocked
21%
Avg conflicts / tx
0.31
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #95,112,277 · 16 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
2w05w06w19w011w114w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3f4f9f22…8ad7
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xe8eae8a3…bacc
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0xf3d10975…0d07
0x34b655…2a6f
4 touches
1 conflict
0xf607560e…828a
0x34b655…2a6f
4 touches
1 conflict
0x356b3121…cf1c
0x34b655…2a6f
4 touches
1 conflict
0x3a5cd535…3546
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: Perpl
1 conflict on slot 0x3f4f9f2274…c88ad7
Audit this contract →
← previous block·next block →recent activity