← previous blocknext block →recent activity
Analyzing
Block #84,526,535
17 transactions · 12 stateful · 2026-06-29 19:22:40 UTC
Parallelism
88/100
Blocked
17%
Avg conflicts / tx
0.12
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #84,526,535 · 17 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w112w013w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x7b9a42f7…7b88
0xa6afd3…d132
4 touches
1 conflict
0x00000000…0002
0xd637b3…4160
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x1c04c6b7…f2b5
0x065c9d…c394
2 touches
0 conflicts
0x21d33a6b…141e
0x065c9d…c394
2 touches
0 conflicts
0x28301ebb…73cc
0x065c9d…c394
2 touches
0 conflicts
0x325e31c0…1726
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: MarginAccount
1 conflict on slot 0xf2f76ab392…f3623e
Audit this contract →
← previous block·next block →recent activity