← previous blocknext block →recent activity
Analyzing
Block #86,700,163
14 transactions · 8 stateful · 2026-07-09 21:03:50 UTC
Parallelism
86/100
Blocked
38%
Avg conflicts / tx
0.21
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,700,163 · 14 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w19w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe0831fb5…bf2f
0x34b655…2a6f
4 touches
1 conflict
0xf3343d6f…bbde
0x34b655…2a6f
4 touches
1 conflict
0xf3343d6f…bbdf
0x34b655…2a6f
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x088e627b…1051
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x56b5f5c0…a3ad
0x34b655…2a6f
4 touches
1 conflict
0x64ac7daf…c064
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
1 conflict on slot 0xe0831fb5c1…8fbf2f
Audit this contract →
← previous block·next block →recent activity