← previous blocknext block →recent activity
Analyzing
Block #80,625,044
25 transactions · 17 stateful · 2026-06-11 17:36:27 UTC
Parallelism
80/100
Blocked
59%
Avg conflicts / tx
0.64
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #80,625,044 · 25 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w26w27w311w012w114w115w420w221w323w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe5060fe3…ebea
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0x17606ba6…1b6e
0x754704…b603
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x91101589…e797
0xd32edf…ff58
5 touches
3 conflicts
0x952f45ec…c54b
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: ShMonad (shMON)
3 conflicts on slot 0xe5060fe3ac…c7ebea
Audit this contract →
← previous block·next block →recent activity