← previous blocknext block →recent activity
Analyzing
Block #75,783,113
17 transactions · 13 stateful · 2026-05-20 07:23:56 UTC
Parallelism
88/100
Blocked
23%
Avg conflicts / tx
0.24
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #75,783,113 · 17 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w110w011w112w013w014w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9b1a47c3…69f8
0xde22b2…7777
4 touches
1 conflict
0x5f77d607…2c84
0x065c9d…c394
4 touches
1 conflict
0x00000000…001e
0x1b6862…e19c
4 touches
1 conflict
0xcb45d9d6…cb86
0x1b6862…e19c
4 touches
1 conflict
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0xa472d565…9fe4
0x3bd359…433a
4 touches
1 conflict
0xbf25e763…684f
0x3bd359…433a
4 touches
1 conflict
0x00000000…0000
0x776059…1d8d
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: MOYAKI (MOYAKI)
1 conflict on slot 0x9b1a47c3d7…c169f8
Audit this contract →
← previous block·next block →recent activity