← previous blocknext block →recent activity
Analyzing
Block #74,518,642
35 transactions · 24 stateful · 2026-05-14 10:29:44 UTC
Parallelism
86/100
Blocked
42%
Avg conflicts / tx
0.57
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #74,518,642 · 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
1w03w04w15w26w37w411w114w215w321w022w131w232w033w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xab3526…fa38
10 touches
10 conflicts
0xa472d565…9fe4
0x3bd359…433a
8 touches
6 conflicts
0x0d622e34…0000
0x681e90…ae09
6 touches
3 conflicts
0x44ad89ba…cf83
0x5c2513…7777
4 touches
1 conflict
0x00000000…0000
0xcc67aa…c71c
4 touches
1 conflict
0x00000000…0001
0xcc67aa…c71c
4 touches
1 conflict
0xce2b6650…ecc3
0x5c2513…7777
4 touches
1 conflict
0x00c46468…f328
0x3bd359…433a
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: 0xab35264b…1cfa38
10 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity