← previous blocknext block →recent activity
Analyzing
Block #73,697,020
27 transactions · 20 stateful · 2026-05-10 15:08:19 UTC
Parallelism
85/100
Blocked
50%
Avg conflicts / tx
0.63
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #73,697,020 · 27 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
1w03w16w014w115w216w317w018w120w021w122w223w325w226w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2438038…5fa7
0x34b655…2a6f
8 touches
6 conflicts
0x6713aa37…fadb
0xd32edf…ff58
7 touches
6 conflicts
0xe6455d1f…1029
0x754704…b603
6 touches
3 conflicts
0x0d0b2509…074d
0x3bd359…433a
6 touches
3 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
4 touches
1 conflict
0x85a88798…f85e
0x34b655…2a6f
4 touches
1 conflict
0x8aa1941d…2988
0x34b655…2a6f
4 touches
1 conflict
0xa8bd52b5…862e
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 0xf2438038b6…475fa7
Audit this contract →
← previous block·next block →recent activity