← previous blocknext block →recent activity
Analyzing
Block #95,646,457
35 transactions · 26 stateful · 2026-08-13 13:44:59 UTC
Parallelism
83/100
Blocked
38%
Avg conflicts / tx
0.51
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #95,646,457 · 35 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w17w08w19w010w011w113w218w219w320w421w325w532w033w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x66d5e476…8a1f
0x34b655…2a6f
8 touches
6 conflicts
0xcb15bf2c…78d1
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0xbab0dbfe…5b0f
0xd32edf…ff58
5 touches
3 conflicts
0x42de1b4a…7fba
0x34b655…2a6f
4 touches
1 conflict
0x43fd3667…094b
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
6 conflicts on slot 0x66d5e476c0…268a1f
Audit this contract →
← previous block·next block →recent activity