← previous blocknext block →recent activity
Analyzing
Block #86,681,232
19 transactions · 14 stateful · 2026-07-09 18:57:33 UTC
Parallelism
89/100
Blocked
29%
Avg conflicts / tx
0.21
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,681,232 · 19 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
1w02w13w08w010w112w117w018w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xd79c9727…1233
0x34b655…2a6f
4 touches
1 conflict
0x4e2fc7ed…c3d1
0xd32edf…ff58
3 touches
1 conflict
0x00000000…0028
0x1b6862…e19c
2 touches
0 conflicts
0xba5743c7…21bf
0x1b6862…e19c
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity