← previous blocknext block →recent activity
Analyzing
Block #75,511,920
20 transactions · 9 stateful · 2026-05-19 01:14:16 UTC
Parallelism
80/100
Blocked
33%
Avg conflicts / tx
0.3
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #75,511,920 · 20 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
5w06w17w28w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x99a3a7c1…1e2b
0x0cc9b2…7777
8 touches
6 conflicts
0x00000000…0000
0x019883…2a9a
8 touches
6 conflicts
0x00000000…0002
0x019883…2a9a
8 touches
6 conflicts
0xa10c86f8…4b74
0x3bd359…433a
8 touches
6 conflicts
0xa472d565…9fe4
0x3bd359…433a
8 touches
6 conflicts
0x44ad89ba…cf83
0x0cc9b2…7777
8 touches
6 conflicts
0x1da1c6cb…bb3f
0x34b655…2a6f
2 touches
0 conflicts
0x2cef1eff…9f14
0x34b655…2a6f
2 touches
0 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: MONI (MONI)
6 conflicts on slot 0x99a3a7c17c…081e2b
Audit this contract →
← previous block·next block →recent activity