← previous blocknext block →recent activity
Analyzing
Block #86,851,403
21 transactions · 16 stateful · 2026-07-10 13:54:23 UTC
Parallelism
76/100
Blocked
44%
Avg conflicts / tx
0.81
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,851,403 · 21 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w15w28w39w010w111w212w318w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd7e4f660…311e
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0000
0x019883…2a9a
8 touches
6 conflicts
0x00000000…0002
0x019883…2a9a
8 touches
6 conflicts
0x00000000…0003
0x019883…2a9a
8 touches
6 conflicts
0x44ad89ba…cf83
0x0cc9b2…7777
8 touches
6 conflicts
0x99a3a7c1…1e2b
0x0cc9b2…7777
8 touches
6 conflicts
0xa472d565…9fe4
0x3bd359…433a
8 touches
6 conflicts
0xa10c86f8…4b74
0x3bd359…433a
8 touches
6 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
6 conflicts on slot 0xd7e4f6607c…4a311e
Audit this contract →
← previous block·next block →recent activity