← previous blocknext block →recent activity
Analyzing
Block #86,136,444
37 transactions · 33 stateful · 2026-07-07 06:15:23 UTC
Parallelism
78/100
Blocked
64%
Avg conflicts / tx
1.19
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #86,136,444 · 37 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w07w38w515w016w117w118w020w122w624w425w727w735w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x28dfe5c9…39e3
0xd32edf…ff58
9 touches
10 conflicts
0xcc8faac2…c766
0x065c9d…c394
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0x18cf3003…51d1
0x065c9d…c394
8 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…001d
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002d
0x1b6862…e19c
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
10 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity