← previous blocknext block →recent activity
Analyzing
Block #84,046,123
24 transactions · 21 stateful · 2026-06-27 14:01:24 UTC
Parallelism
67/100
Blocked
33%
Avg conflicts / tx
1.17
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #84,046,123 · 24 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
1w02w13w24w35w46w57w68w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…000a
0x90c374…be45
16 touches
28 conflicts
0x00000000…000b
0x90c374…be45
16 touches
28 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x30215095…d0ec
0x065c9d…c394
2 touches
0 conflicts
0x8cd948dc…15f6
0x065c9d…c394
2 touches
0 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
2 touches
0 conflicts
0x10f3a178…e865
0x336ed4…c59c
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: 0x90c3747c…0ebe45
28 conflicts on slot 0x0000000000…00000a
Audit this contract →
← previous block·next block →recent activity