← previous blocknext block →recent activity
Analyzing
Block #95,086,015
14 transactions · 12 stateful · 2026-08-11 14:32:27 UTC
Parallelism
57/100
Blocked
42%
Avg conflicts / tx
0.93
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #95,086,015 · 14 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
1w02w16w27w38w49w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x38bdc5d3…a632
0x34b655…2a6f
10 touches
10 conflicts
0xa1850959…7c77
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x9ac6d391…82f1
0x34b655…2a6f
6 touches
3 conflicts
0xbaf77397…e798
0x34b655…2a6f
4 touches
1 conflict
0xa214976d…5939
0x34b655…2a6f
2 touches
0 conflicts
0xd66696e0…0842
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
10 conflicts on slot 0x38bdc5d3e1…01a632
Audit this contract →
← previous block·next block →recent activity