← previous blocknext block →recent activity
Analyzing
Block #74,775,524
35 transactions · 25 stateful · 2026-05-15 15:09:02 UTC
Parallelism
86/100
Blocked
44%
Avg conflicts / tx
0.57
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #74,775,524 · 35 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
6w011w012w115w016w117w018w119w020w121w222w323w230w131w232w333w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00c46468…f328
0x3bd359…433a
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0000
0xcc67aa…c71c
8 touches
6 conflicts
0xce2b6650…ecc3
0x5c2513…7777
8 touches
6 conflicts
0x44ad89ba…cf83
0x5c2513…7777
8 touches
6 conflicts
0x00000000…0001
0xcc67aa…c71c
8 touches
6 conflicts
0xa472d565…9fe4
0x3bd359…433a
8 touches
6 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 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)
6 conflicts on slot 0x00c46468d1…54f328
Audit this contract →
← previous block·next block →recent activity