← previous blocknext block →recent activity
Analyzing
Block #84,290,810
22 transactions · 20 stateful · 2026-06-28 17:11:12 UTC
Parallelism
73/100
Blocked
45%
Avg conflicts / tx
0.82
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #84,290,810 · 22 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w16w010w112w213w315w416w219w120w221w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2f76ab3…623e
0x2a68ba…90c5
10 touches
10 conflicts
0xa9db7b4d…2957
0x40c49f…2af0
6 touches
3 conflicts
0xdfc5f346…7b42
0x40c49f…2af0
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xaa99c864…a228
0x34b655…2a6f
4 touches
1 conflict
0xcc2cd268…5687
0x34b655…2a6f
4 touches
1 conflict
0xd01910c9…9418
0x34b655…2a6f
4 touches
1 conflict
0xd58b9a66…1c23
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: Kuru Exchange: MarginAccount
10 conflicts on slot 0xf2f76ab392…f3623e
Audit this contract →
← previous block·next block →recent activity