← previous blocknext block →recent activity
Analyzing
Block #84,253,351
22 transactions · 20 stateful · 2026-06-28 13:01:37 UTC
Parallelism
64/100
Blocked
60%
Avg conflicts / tx
1.77
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #84,253,351 · 22 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
1w02w06w17w18w29w010w211w312w413w514w616w119w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2f76ab3…623e
0x2a68ba…90c5
16 touches
28 conflicts
0x5df6102c…6494
0xa6afd3…d132
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xf3c944ab…2aaf
0x065c9d…c394
6 touches
3 conflicts
0xa9db7b4d…2957
0x40c49f…2af0
6 touches
3 conflicts
0xa1087a5c…66c4
0x754704…b603
6 touches
3 conflicts
0x22e0cc1d…ad0d
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
28 conflicts on slot 0xf2f76ab392…f3623e
Audit this contract →
← previous block·next block →recent activity