← previous blocknext block →recent activity
Analyzing
Block #74,647,083
22 transactions · 16 stateful · 2026-05-15 00:51:11 UTC
Parallelism
82/100
Blocked
44%
Avg conflicts / tx
0.55
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #74,647,083 · 22 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
1w02w06w18w19w010w111w212w318w020w221w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60f7fbaf…bd58
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x3b3a5945…10d0
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0002
0xab3526…fa38
4 touches
1 conflict
0x37674bd8…8f35
0x34b655…2a6f
4 touches
1 conflict
0x94710b77…a921
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0x0d622e34…0000
0x681e90…ae09
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 0x60f7fbaf90…97bd58
Audit this contract →
← previous block·next block →recent activity