← previous blocknext block →recent activity
Analyzing
Block #86,054,407
21 transactions · 19 stateful · 2026-07-06 21:08:00 UTC
Parallelism
90/100
Blocked
16%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,054,407 · 21 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
4w06w07w113w117w018w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd6d040d9…9ae3
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xec0e0220…cb90
0x34b655…2a6f
4 touches
1 conflict
0x23a79489…1a00
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x2dff59d9…f5e6
0x34b655…2a6f
4 touches
1 conflict
0x76ed8777…1e5f
0x34b655…2a6f
4 touches
1 conflict
0x91ff239c…e07b
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 0xd6d040d989…9c9ae3
Audit this contract →
← previous block·next block →recent activity