← previous blocknext block →recent activity
Analyzing
Block #84,289,670
33 transactions · 20 stateful · 2026-06-28 17:03:35 UTC
Parallelism
85/100
Blocked
45%
Avg conflicts / tx
0.58
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #84,289,670 · 33 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w05w16w27w28w313w014w116w431w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7d42dc8b…fdb6
0x2a68ba…90c5
8 touches
6 conflicts
0x56785e37…a197
0x065c9d…c394
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x4039b31f…0f4a
0x754704…b603
6 touches
3 conflicts
0x00000000…0004
0x5afd3e…7620
6 touches
3 conflicts
0x55654c34…5183
0xd32edf…ff58
5 touches
3 conflicts
0x00000000…0028
0x1b6862…e19c
4 touches
1 conflict
0x44d7acbf…e67a
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: Kuru Exchange: MarginAccount
6 conflicts on slot 0x7d42dc8b22…fefdb6
Audit this contract →
← previous block·next block →recent activity