← previous blocknext block →recent activity
Analyzing
Block #73,807,463
41 transactions · 30 stateful · 2026-05-11 03:33:16 UTC
Parallelism
68/100
Blocked
73%
Avg conflicts / tx
1.88
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #73,807,463 · 41 txs across 13 waves · depth 13
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w17w08w09w115w117w219w020w121w222w323w424w525w626w227w328w429w533w635w737w938w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9db64d13…fb98
0x34b655…2a6f
14 touches
21 conflicts
0x7753d7bf…3ff9
0xd32edf…ff58
13 touches
21 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
12 touches
15 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0xac2a0273…721b
0x34b655…2a6f
10 touches
10 conflicts
0x15c9b5bf…f732
0x34b655…2a6f
8 touches
6 conflicts
0xc08f0dac…68aa
0x34b655…2a6f
8 touches
6 conflicts
0x664bf99e…0a8c
0x34b655…2a6f
8 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: Perpl
21 conflicts on slot 0x9db64d13f5…6efb98
Audit this contract →
← previous block·next block →recent activity