← previous blocknext block →recent activity
Analyzing
Block #84,513,879
17 transactions · 16 stateful · 2026-06-29 17:58:19 UTC
Parallelism
82/100
Blocked
31%
Avg conflicts / tx
0.29
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #84,513,879 · 17 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w16w09w110w211w012w115w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x489cb750…7069
0x065c9d…c394
4 touches
1 conflict
0x26918bca…6c75
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x89ef0dba…31e2
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0xdb067026…9eb8
0x69df8a…6292
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
1 conflict on slot 0x489cb75090…f57069
Audit this contract →
← previous block·next block →recent activity