← previous blocknext block →recent activity
Analyzing
Block #84,282,468
13 transactions · 11 stateful · 2026-06-28 16:15:36 UTC
Parallelism
62/100
Blocked
36%
Avg conflicts / tx
0.62
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #84,282,468 · 13 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
1w02w16w27w38w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0x56785e37…a197
0x065c9d…c394
4 touches
1 conflict
0xb3ad6aff…7a71
0x065c9d…c394
4 touches
1 conflict
0xaabff67a…5e3e
0x065c9d…c394
3 touches
1 conflict
0x496bdd4a…d57e
0x065c9d…c394
3 touches
1 conflict
0x58f2fdac…ae86
0x065c9d…c394
2 touches
0 conflicts
0x7ea43b0d…6f76
0x065c9d…c394
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: Kuru Exchange: Market-MON/USDC
6 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity