← previous blocknext block →recent activity
Analyzing
Block #74,938,054
56 transactions · 47 stateful · 2026-05-16 09:13:13 UTC
Parallelism
63/100
Blocked
77%
Avg conflicts / tx
3.82
Longest chain
21 deep
Execution timeline
did this block parallelize well?
view
block #74,938,054 · 56 txs across 21 waves · depth 21
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
wave w19
wave w20
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w59w614w615w741w642w843w944w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60f7fbaf…bd58
0x34b655…2a6f
30 touches
105 conflicts
0x06b54ec0…c3e4
0xd32edf…ff58
19 touches
45 conflicts
0x00000000…0013
0x1b6862…e19c
16 touches
28 conflicts
0xeb0915f1…c150
0x34b655…2a6f
16 touches
28 conflicts
0x664bf99e…0a8c
0x34b655…2a6f
16 touches
28 conflicts
0x7cb2f3fa…4836
0x34b655…2a6f
16 touches
28 conflicts
0xd18a8dca…452e
0x1b6862…e19c
16 touches
28 conflicts
0x10f5f4d8…572e
0x34b655…2a6f
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: Perpl
105 conflicts on slot 0x60f7fbaf90…97bd58
Audit this contract →
← previous block·next block →recent activity