← previous blocknext block →recent activity
Analyzing
Block #74,224,537
17 transactions · 15 stateful · 2026-05-13 01:51:34 UTC
Parallelism
76/100
Blocked
53%
Avg conflicts / tx
0.82
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #74,224,537 · 17 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w15w06w17w29w313w014w115w216w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x768cffcd…2648
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
8 touches
6 conflicts
0xaf498679…7732
0x34b655…2a6f
6 touches
3 conflicts
0xcd5c7f64…ad4b
0x34b655…2a6f
6 touches
3 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x3b3a5945…10d0
0x34b655…2a6f
4 touches
1 conflict
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
6 conflicts on slot 0x768cffcdb0…d12648
Audit this contract →
← previous block·next block →recent activity