← previous blocknext block →recent activity
Analyzing
Block #86,797,329
15 transactions · 12 stateful · 2026-07-10 07:52:49 UTC
Parallelism
73/100
Blocked
33%
Avg conflicts / tx
0.27
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,797,329 · 15 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w18w010w113w214w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xded7831c…3c4a
0x34b655…2a6f
4 touches
1 conflict
0xe0556bea…a4c8
0x34b655…2a6f
4 touches
1 conflict
0x0b9f02c4…6fec
0x34b655…2a6f
4 touches
1 conflict
0x12205b11…edd1
0x34b655…2a6f
4 touches
1 conflict
0x19ad864c…c5cb
0x34b655…2a6f
4 touches
1 conflict
0x1d84bebc…07d0
0x34b655…2a6f
4 touches
1 conflict
0x1d84bebc…07d1
0x34b655…2a6f
4 touches
1 conflict
0x3cef6445…87da
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 0xded7831cbc…d33c4a
Audit this contract →
← previous block·next block →recent activity