← previous blocknext block →recent activity
Analyzing
Block #74,762,382
48 transactions · 44 stateful · 2026-05-15 13:41:01 UTC
Parallelism
60/100
Blocked
75%
Avg conflicts / tx
4.5
Longest chain
19 deep
Execution timeline
did this block parallelize well?
view
block #74,762,382 · 48 txs across 19 waves · depth 19
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
wave w15
wave w16
wave w17
wave w18
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w05w16w27w38w49w510w611w712w813w914w1015w1116w1217w1318w1419w1520w1621w1722w1823w329w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0001
0x86dfd5…6a7d
38 touches
171 conflicts
0x1d4c90ab…1ba7
0xb72e62…7777
38 touches
171 conflicts
0x00000000…0003
0x86dfd5…6a7d
38 touches
171 conflicts
0x00000000…0000
0x86dfd5…6a7d
38 touches
171 conflicts
0x1686502b…a1d2
0x3bd359…433a
38 touches
171 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
16 touches
28 conflicts
0xb9868b52…c77f
0x34b655…2a6f
10 touches
10 conflicts
0xbe34086c…c136
0xd32edf…ff58
7 touches
6 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: 0x86dfd554…906a7d
171 conflicts on slot 0x0000000000…000001
Audit this contract →
← previous block·next block →recent activity