← previous blocknext block →recent activity
Analyzing
Block #86,697,103
14 transactions · 11 stateful · 2026-07-09 20:43:24 UTC
Parallelism
71/100
Blocked
45%
Avg conflicts / tx
0.57
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,697,103 · 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
1w02w13w24w07w08w19w210w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd7e0d683…1f5a
0x34b655…2a6f
6 touches
3 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 conflicts
0x0ed7cc0b…ee52
0x34b655…2a6f
4 touches
1 conflict
0x178fca0f…e418
0x34b655…2a6f
4 touches
1 conflict
0x454cdf57…aebc
0x34b655…2a6f
4 touches
1 conflict
0x4cf39eee…2213
0x34b655…2a6f
4 touches
1 conflict
0x6247f215…3d1c
0x34b655…2a6f
4 touches
1 conflict
0x75eb421e…ccae
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
3 conflicts on slot 0xd7e0d6838d…bb1f5a
Audit this contract →
← previous block·next block →recent activity