← previous blocknext block →recent activity
Analyzing
Block #83,890,582
18 transactions · 17 stateful · 2026-06-26 20:45:04 UTC
Parallelism
67/100
Blocked
53%
Avg conflicts / tx
0.67
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #83,890,582 · 18 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w06w18w09w110w311w312w413w214w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfac61869…a55b
0x1b6862…e19c
6 touches
3 conflicts
0xff96dc9b…93d7
0x065c9d…c394
6 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0018
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0028
0x1b6862…e19c
6 touches
3 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: ShMonad (shMON)
3 conflicts on slot 0xfac61869bf…30a55b
Audit this contract →
← previous block·next block →recent activity