← previous blocknext block →recent activity
Analyzing
Block #95,154,318
9 transactions · 6 stateful · 2026-08-11 20:16:02 UTC
Parallelism
78/100
Blocked
17%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #95,154,318 · 9 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
4w05w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd6db9d1c…2f38
0x34b655…2a6f
4 touches
1 conflict
0xd6db9d1c…2f37
0x34b655…2a6f
4 touches
1 conflict
0x5d6e4470…4b4c
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x55d9e819…edd5
0x34b655…2a6f
3 touches
1 conflict
0x7588a4ef…a032
0x34b655…2a6f
3 touches
1 conflict
0x9d80eb2c…66ec
0x34b655…2a6f
3 touches
1 conflict
0x4f4bdabd…ffba
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 0xd6db9d1c5b…002f38
Audit this contract →
← previous block·next block →recent activity