← previous blocknext block →recent activity
Analyzing
Block #86,849,570
31 transactions · 27 stateful · 2026-07-10 13:42:08 UTC
Parallelism
84/100
Blocked
44%
Avg conflicts / tx
0.77
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,849,570 · 31 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
1w04w15w06w17w210w111w212w013w114w218w022w323w127w028w229w330w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xf3d10975…0d07
0x34b655…2a6f
8 touches
6 conflicts
0xea02471d…1542
0x34b655…2a6f
8 touches
6 conflicts
0x80943c84…97d6
0xd32edf…ff58
7 touches
6 conflicts
0xcb45d9d6…cb83
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0002
0x04fdea…47d7
6 touches
3 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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity