← previous blocknext block →recent activity
Analyzing
Block #86,103,334
37 transactions · 27 stateful · 2026-07-07 02:34:16 UTC
Parallelism
92/100
Blocked
37%
Avg conflicts / tx
0.32
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,103,334 · 37 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
1w04w05w06w07w19w010w112w117w123w124w229w230w232w033w135w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xd9a3c8d2…0a45
0xd32edf…ff58
5 touches
3 conflicts
0x18cf3003…51d1
0x065c9d…c394
4 touches
1 conflict
0x42e5ad32…6947
0x065c9d…c394
4 touches
1 conflict
0xcc8faac2…c766
0x065c9d…c394
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x1b5d2e60…99b5
0x34b655…2a6f
4 touches
1 conflict
0x442e26a3…e968
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
3 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity