← previous blocknext block →recent activity
Analyzing
Block #76,676,970
41 transactions · 24 stateful · 2026-05-24 10:38:17 UTC
Parallelism
88/100
Blocked
54%
Avg conflicts / tx
0.63
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #76,676,970 · 41 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
2w05w06w17w28w311w112w213w314w018w019w120w221w322w437w139w240w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa472d565…9fe4
0x3bd359…433a
10 touches
10 conflicts
0x3c251e5a…0218
0x6a13bf…7777
10 touches
10 conflicts
0x877b0dd6…84c6
0x3bd359…433a
10 touches
10 conflicts
0x44ad89ba…cf83
0x6a13bf…7777
10 touches
10 conflicts
0x00000000…0000
0x139aab…382b
10 touches
10 conflicts
0x00000000…0001
0x139aab…382b
10 touches
10 conflicts
0x00000000…0003
0x139aab…382b
10 touches
10 conflicts
0xcc4f1f14…aa5f
0x065c9d…c394
8 touches
6 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: Wrapped MON (WMON)
10 conflicts on slot 0xa472d565a0…ae9fe4
Audit this contract →
← previous block·next block →recent activity