← previous blocknext block →recent activity
Analyzing
Block #95,902,907
10 transactions · 8 stateful · 2026-08-14 11:16:04 UTC
Parallelism
70/100
Blocked
38%
Avg conflicts / tx
0.3
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #95,902,907 · 10 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w17w18w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x69e18150…e65f
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0xa940f3a4…c5e7
0x34b655…2a6f
4 touches
1 conflict
0xa940f3a4…c5e8
0x34b655…2a6f
4 touches
1 conflict
0xadc05b3e…378d
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xd82d1c5a…0850
0x34b655…2a6f
4 touches
1 conflict
0x70664c87…57b6
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 0x69e18150e1…cfe65f
Audit this contract →
← previous block·next block →recent activity