← previous blocknext block →recent activity
Analyzing
Block #86,340,749
16 transactions · 16 stateful · 2026-07-08 04:59:35 UTC
Parallelism
88/100
Blocked
19%
Avg conflicts / tx
0.19
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,340,749 · 16 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
1w03w04w19w110w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4bfdcd51…9b58
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xcc8faac2…c766
0x065c9d…c394
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
2 touches
0 conflicts
0x042a03b5…5665
0x065c9d…c394
2 touches
0 conflicts
0x0c6e02dc…5721
0x065c9d…c394
2 touches
0 conflicts
0x39290af4…a5d9
0x065c9d…c394
2 touches
0 conflicts
0x7f0540e1…ff02
0x065c9d…c394
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 0x4bfdcd5135…769b58
Audit this contract →
← previous block·next block →recent activity