← previous blocknext block →recent activity
Analyzing
Block #74,781,603
58 transactions · 48 stateful · 2026-05-15 15:49:36 UTC
Parallelism
71/100
Blocked
83%
Avg conflicts / tx
3.48
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #74,781,603 · 58 txs across 17 waves · depth 17
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w68w717w818w940w741w842w1044w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xab3526…fa38
22 touches
55 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
20 touches
45 conflicts
0x1280574e…c577
0xd32edf…ff58
19 touches
45 conflicts
0xba5743c7…21c1
0x1b6862…e19c
18 touches
36 conflicts
0x00000000…0013
0x1b6862…e19c
18 touches
36 conflicts
0x00000000…0015
0x1b6862…e19c
18 touches
36 conflicts
0x00000000…002a
0x1b6862…e19c
16 touches
28 conflicts
0x00000000…0012
0x1b6862…e19c
16 touches
28 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: 0xab35264b…1cfa38
55 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity