← previous blocknext block →recent activity
Analyzing
Block #83,958,378
14 transactions · 12 stateful · 2026-06-27 04:16:50 UTC
Parallelism
79/100
Blocked
25%
Avg conflicts / tx
0.21
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #83,958,378 · 14 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w16w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x79cbb230…1121
0x065c9d…c394
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0xff96dc9b…93d7
0x065c9d…c394
4 touches
1 conflict
0x00000000…0002
0xd637b3…4160
4 touches
1 conflict
0xd3c72973…d1a3
0x065c9d…c394
3 touches
1 conflict
0x3c5630bd…5be1
0x065c9d…c394
3 touches
1 conflict
0x6b01e8e5…c1a6
0x065c9d…c394
3 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
1 conflict on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity