← previous blocknext block →recent activity
Analyzing
Block #86,756,229
10 transactions · 9 stateful · 2026-07-10 03:18:30 UTC
Parallelism
80/100
Blocked
22%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,756,229 · 10 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
4w05w17w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x013c31f5…a718
0x34b655…2a6f
4 touches
1 conflict
0xc0454af2…07ca
0x34b655…2a6f
4 touches
1 conflict
0xc7fed9f9…f3a0
0x34b655…2a6f
4 touches
1 conflict
0x5a576152…6d63
0x34b655…2a6f
4 touches
1 conflict
0x013c31f5…a717
0x34b655…2a6f
4 touches
1 conflict
0x4edc5bf0…b281
0x34b655…2a6f
3 touches
1 conflict
0x1c03f81f…b304
0x34b655…2a6f
2 touches
0 conflicts
0x30f36778…aead
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
1 conflict on slot 0x013c31f575…6ba718
Audit this contract →
← previous block·next block →recent activity