← previous blocknext block →recent activity
Analyzing
Block #95,383,229
13 transactions · 11 stateful · 2026-08-12 15:39:46 UTC
Parallelism
77/100
Blocked
27%
Avg conflicts / tx
0.31
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #95,383,229 · 13 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
2w05w06w17w18w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbef1e8f5…ae70
0x34b655…2a6f
6 touches
3 conflicts
0x226ae29a…2612
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721c
0x34b655…2a6f
4 touches
1 conflict
0xdd86c376…5df8
0x968279…9342
4 touches
1 conflict
0xdd86c376…5df5
0x968279…9342
4 touches
1 conflict
0xdd86c376…5df6
0x968279…9342
4 touches
1 conflict
0xc755c95b…6814
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 0xbef1e8f550…d4ae70
Audit this contract →
← previous block·next block →recent activity