← previous blocknext block →recent activity
Analyzing
Block #75,525,499
16 transactions · 13 stateful · 2026-05-19 02:47:14 UTC
Parallelism
56/100
Blocked
54%
Avg conflicts / tx
1.38
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #75,525,499 · 16 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w06w17w28w39w410w511w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x44ad89ba…cf83
0x0cc9b2…7777
14 touches
21 conflicts
0xa472d565…9fe4
0x3bd359…433a
14 touches
21 conflicts
0xa10c86f8…4b74
0x3bd359…433a
14 touches
21 conflicts
0x00000000…0000
0x019883…2a9a
14 touches
21 conflicts
0x00000000…0002
0x019883…2a9a
14 touches
21 conflicts
0x99a3a7c1…1e2b
0x0cc9b2…7777
14 touches
21 conflicts
0x76074be2…8e88
0xd32edf…ff58
3 touches
1 conflict
0x5f77d607…2c84
0x065c9d…c394
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)
21 conflicts on slot 0x44ad89ba62…49cf83
Audit this contract →
← previous block·next block →recent activity