← previous blocknext block →recent activity
Analyzing
Block #72,980,038
19 transactions · 16 stateful · 2026-05-07 07:31:39 UTC
Parallelism
68/100
Blocked
50%
Avg conflicts / tx
1.11
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #72,980,038 · 19 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
1w02w03w14w16w07w112w013w114w216w317w418w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0x4b268018…02fb
0x34b655…2a6f
6 touches
3 conflicts
0x35b85d8e…1edd
0x34b655…2a6f
4 touches
1 conflict
0x38441f18…60e5
0x34b655…2a6f
4 touches
1 conflict
0x60f7fbaf…bd58
0x34b655…2a6f
4 touches
1 conflict
0xa30bf225…a650
0x34b655…2a6f
4 touches
1 conflict
0xcf17589f…048c
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
15 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity