← previous blocknext block →recent activity
Analyzing
Block #74,915,687
29 transactions · 26 stateful · 2026-05-16 06:43:57 UTC
Parallelism
35/100
Blocked
69%
Avg conflicts / tx
5.34
Longest chain
19 deep
Execution timeline
did this block parallelize well?
view
block #74,915,687 · 29 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
4w05w16w27w38w49w510w611w712w813w914w1015w1116w1217w1318w1425w1527w1728w18
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x388e001a…7e04
0x34b655…2a6f
30 touches
105 conflicts
0xc6417de0…2191
0xc8689a…ee79
30 touches
105 conflicts
0x660b3c19…372a
0x34b655…2a6f
28 touches
91 conflicts
0x0711ec2d…d973
0x34b655…2a6f
24 touches
66 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
24 touches
66 conflicts
0xd49762c9…1359
0x34b655…2a6f
24 touches
66 conflicts
0x9be2b99a…a959
0x34b655…2a6f
24 touches
66 conflicts
0x8db1e0f2…2fcf
0x34b655…2a6f
24 touches
66 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 0x388e001a16…e57e04
Audit this contract →
← previous block·next block →recent activity