← previous blocknext block →recent activity
Analyzing
Block #73,036,614
25 transactions · 20 stateful · 2026-05-07 13:48:13 UTC
Parallelism
76/100
Blocked
50%
Avg conflicts / tx
0.72
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #73,036,614 · 25 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w04w16w28w112w013w114w215w318w122w223w424w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60f7fbaf…bd58
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0002
0xd574ca…7ab1
6 touches
3 conflicts
0x388e001a…7e04
0x34b655…2a6f
6 touches
3 conflicts
0x61ad45b1…15ac
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xdaca243a…f9de
0x34b655…2a6f
6 touches
3 conflicts
0x3702b140…97ea
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