← previous blocknext block →recent activity
Analyzing
Block #95,087,279
19 transactions · 18 stateful · 2026-08-11 14:38:49 UTC
Parallelism
63/100
Blocked
39%
Avg conflicts / tx
0.74
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #95,087,279 · 19 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w08w39w410w511w618w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x39146670…bc53
0x34b655…2a6f
8 touches
6 conflicts
0x07d8b1e8…78c6
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x6c60fbcf…8744
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x0140fbd3…d957
0x34b655…2a6f
4 touches
1 conflict
0x40a9339c…6571
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 0x3914667037…e5bc53
Audit this contract →
← previous block·next block →recent activity