← previous blocknext block →recent activity
Analyzing
Block #86,056,526
26 transactions · 23 stateful · 2026-07-06 21:22:07 UTC
Parallelism
88/100
Blocked
39%
Avg conflicts / tx
0.46
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,056,526 · 26 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w26w07w114w218w119w122w123w024w125w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xdd70bea3…1ffe
0x3bd359…433a
6 touches
3 conflicts
0x292d61c9…e309
0xd32edf…ff58
5 touches
3 conflicts
0x95523e2a…4c01
0x065c9d…c394
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x77ed432f…fa04
0x065c9d…c394
4 touches
1 conflict
0x00000000…002c
0x1b6862…e19c
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
3 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity