← previous blocknext block →recent activity
Analyzing
Block #95,575,489
14 transactions · 14 stateful · 2026-08-13 07:48:01 UTC
Parallelism
71/100
Blocked
29%
Avg conflicts / tx
0.29
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #95,575,489 · 14 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w37w08w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2840c278…bbc7
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xb3fb9fb5…64db
0x34b655…2a6f
4 touches
1 conflict
0x43fd3667…094b
0x34b655…2a6f
4 touches
1 conflict
0x69c491e3…98d9
0x34b655…2a6f
2 touches
0 conflicts
0x71f4c564…5b6b
0x34b655…2a6f
2 touches
0 conflicts
0x97724ab3…495f
0x34b655…2a6f
2 touches
0 conflicts
0xaa4407fb…5f2e
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 0x2840c278a3…01bbc7
Audit this contract →
← previous block·next block →recent activity