← previous blocknext block →recent activity
Analyzing
Block #83,876,402
24 transactions · 24 stateful · 2026-06-26 19:10:29 UTC
Parallelism
83/100
Blocked
38%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #83,876,402 · 24 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
1w02w03w14w05w17w08w112w014w215w016w117w118w119w321w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0b16149e…7d4d
0x065c9d…c394
6 touches
3 conflicts
0x00000000…0002
0xd637b3…4160
4 touches
1 conflict
0x5df6102c…6494
0xa6afd3…d132
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0018
0x1b6862…e19c
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
3 conflicts on slot 0x0b16149e0d…887d4d
Audit this contract →
← previous block·next block →recent activity