← previous blocknext block →recent activity
Analyzing
Block #84,240,138
11 transactions · 11 stateful · 2026-06-28 11:33:40 UTC
Parallelism
82/100
Blocked
18%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #84,240,138 · 11 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
2w04w05w16w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xff96dc9b…93d7
0x065c9d…c394
4 touches
1 conflict
0xbd68c7c7…40b3
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xeefeb1fb…85b4
0x065c9d…c394
4 touches
1 conflict
0x6524e735…f150
0x065c9d…c394
3 touches
1 conflict
0x95058517…d57f
0x065c9d…c394
3 touches
1 conflict
0x5632cbb0…25ba
0x065c9d…c394
3 touches
1 conflict
0xf8abba47…da51
0x065c9d…c394
3 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: Market-MON/USDC
1 conflict on slot 0xff96dc9b2f…5a93d7
Audit this contract →
← previous block·next block →recent activity