← previous blocknext block →recent activity
Analyzing
Block #83,932,225
10 transactions · 9 stateful · 2026-06-27 01:22:29 UTC
Parallelism
80/100
Blocked
11%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #83,932,225 · 10 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
1w05w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfe7e2dbc…befb
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0xc4b3c54b…8a1c
0x065c9d…c394
4 touches
1 conflict
0x0ad4dbe8…ae93
0x34b655…2a6f
2 touches
0 conflicts
0x19bfb0e5…73b4
0x34b655…2a6f
2 touches
0 conflicts
0x206fb8db…a146
0x34b655…2a6f
2 touches
0 conflicts
0x5b47a6fb…f5bf
0x34b655…2a6f
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 0xfe7e2dbc48…5ebefb
Audit this contract →
← previous block·next block →recent activity