← previous blocknext block →recent activity
Analyzing
Block #84,200,110
17 transactions · 17 stateful · 2026-06-28 07:06:47 UTC
Parallelism
76/100
Blocked
18%
Avg conflicts / tx
0.29
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #84,200,110 · 17 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w09w111w212w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x56785e37…a197
0x065c9d…c394
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x2fa2e79b…56a4
0x065c9d…c394
2 touches
0 conflicts
0x416a0243…c97d
0x065c9d…c394
2 touches
0 conflicts
0x8bccdd6e…17b2
0x065c9d…c394
2 touches
0 conflicts
0xa5954200…937f
0x065c9d…c394
2 touches
0 conflicts
0x01a89030…f786
0x368ee5…7ca4
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
3 conflicts on slot 0x56785e3778…33a197
Audit this contract →
← previous block·next block →recent activity