← previous blocknext block →recent activity
Analyzing
Block #83,493,812
17 transactions · 15 stateful · 2026-06-25 00:37:40 UTC
Parallelism
76/100
Blocked
27%
Avg conflicts / tx
0.47
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #83,493,812 · 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
2w04w05w17w28w315w016w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xdc8d4ee0…def3
0x34b655…2a6f
4 touches
1 conflict
0xe6a0d26a…8ae6
0x34b655…2a6f
4 touches
1 conflict
0x1d0ce76d…6e77
0x065c9d…c394
4 touches
1 conflict
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0x7ee6007b…fd68
0x34b655…2a6f
4 touches
1 conflict
0x9863393c…ce7b
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
6 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity