← previous blocknext block →recent activity
Analyzing
Block #83,666,954
16 transactions · 15 stateful · 2026-06-25 19:52:57 UTC
Parallelism
88/100
Blocked
7%
Avg conflicts / tx
0.06
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #83,666,954 · 16 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
1w03w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x56785e37…a197
0x065c9d…c394
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x11be29f1…484e
0x065c9d…c394
2 touches
0 conflicts
0x581e1030…2a7f
0x065c9d…c394
2 touches
0 conflicts
0x84259a12…9c95
0x065c9d…c394
2 touches
0 conflicts
0xcd141e62…7a29
0x065c9d…c394
2 touches
0 conflicts
0xeaeb4d63…b19d
0x065c9d…c394
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 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity