← previous blocknext block →recent activity
Analyzing
Block #95,217,156
14 transactions · 13 stateful · 2026-08-12 01:32:05 UTC
Parallelism
64/100
Blocked
38%
Avg conflicts / tx
0.64
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #95,217,156 · 14 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w06w17w19w210w311w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x41c8951d…808e
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xa779293b…5e59
0x34b655…2a6f
6 touches
3 conflicts
0xa53c3cca…db68
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0x0884f810…2983
0x34b655…2a6f
4 touches
1 conflict
0x0d481dec…5ccd
0x34b655…2a6f
4 touches
1 conflict
0x1507536e…933f
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
3 conflicts on slot 0x41c8951d7e…4e808e
Audit this contract →
← previous block·next block →recent activity