← previous blocknext block →recent activity
Analyzing
Block #84,513,101
34 transactions · 26 stateful · 2026-06-29 17:53:06 UTC
Parallelism
79/100
Blocked
50%
Avg conflicts / tx
0.76
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #84,513,101 · 34 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w28w09w110w011w215w016w122w023w124w225w128w330w331w432w533w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
10 touches
10 conflicts
0x0b16149e…7d4d
0x065c9d…c394
10 touches
10 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
6 touches
3 conflicts
0x0cfb5337…cfc2
0xd32edf…ff58
5 touches
3 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x2877f440…c2c8
0x34b655…2a6f
4 touches
1 conflict
0x2d943d78…3784
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: Market-MON/USDC
10 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity