← previous blocknext block →recent activity
Analyzing
Block #74,773,246
30 transactions · 19 stateful · 2026-05-15 14:53:47 UTC
Parallelism
77/100
Blocked
37%
Avg conflicts / tx
0.73
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #74,773,246 · 30 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
14w015w116w217w318w419w520w628w029w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0000
0xcc67aa…c71c
14 touches
21 conflicts
0xa472d565…9fe4
0x3bd359…433a
14 touches
21 conflicts
0x00c46468…f328
0x3bd359…433a
14 touches
21 conflicts
0xce2b6650…ecc3
0x5c2513…7777
14 touches
21 conflicts
0x00000000…0001
0xcc67aa…c71c
14 touches
21 conflicts
0x44ad89ba…cf83
0x5c2513…7777
14 touches
21 conflicts
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0x25f0fcba…ca8b
0x34b655…2a6f
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: 0xcc67aab1…cac71c
21 conflicts on slot 0x0000000000…000000
Audit this contract →
← previous block·next block →recent activity