← previous blocknext block →recent activity
Analyzing
Block #86,945,678
15 transactions · 13 stateful · 2026-07-11 00:24:40 UTC
Parallelism
73/100
Blocked
38%
Avg conflicts / tx
0.67
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,945,678 · 15 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
2w04w05w17w29w311w012w113w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0733be30…112f
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x42041fec…bd86
0x754704…b603
6 touches
3 conflicts
0x6e303d0b…01bb
0x34b655…2a6f
6 touches
3 conflicts
0x86f32276…0ebf
0x34b655…2a6f
4 touches
1 conflict
0x98460be4…2ef8
0x34b655…2a6f
4 touches
1 conflict
0xc5f336ca…912e
0x34b655…2a6f
4 touches
1 conflict
0xecb22834…eedb
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 0x0733be30d6…38112f
Audit this contract →
← previous block·next block →recent activity