← previous blocknext block →recent activity
Analyzing
Block #74,451,379
26 transactions · 23 stateful · 2026-05-14 03:00:39 UTC
Parallelism
65/100
Blocked
48%
Avg conflicts / tx
1.54
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #74,451,379 · 26 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w27w38w49w510w611w712w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xab3526…fa38
18 touches
36 conflicts
0x00000000…0000
0xcc67aa…c71c
6 touches
3 conflicts
0x00c46468…f328
0x3bd359…433a
6 touches
3 conflicts
0x00000000…0001
0xcc67aa…c71c
6 touches
3 conflicts
0xce2b6650…ecc3
0x5c2513…7777
6 touches
3 conflicts
0x44ad89ba…cf83
0x5c2513…7777
6 touches
3 conflicts
0xa472d565…9fe4
0x3bd359…433a
6 touches
3 conflicts
0xc08384da…ecb7
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: 0xab35264b…1cfa38
36 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity