← previous blocknext block →recent activity
Analyzing
Block #72,233,870
31 transactions · 26 stateful · 2026-05-03 20:36:46 UTC
Parallelism
87/100
Blocked
54%
Avg conflicts / tx
0.81
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #72,233,870 · 31 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
1w03w04w05w06w17w08w19w213w014w115w016w117w218w319w322w123w224w325w229w230w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60f7fbaf…bd58
0x34b655…2a6f
8 touches
6 conflicts
0x8a35acfb…d1ab
0x8d66a4…3095
8 touches
6 conflicts
0x1c389468…6b0e
0x34b655…2a6f
6 touches
3 conflicts
0x17606ba6…1b6e
0x754704…b603
6 touches
3 conflicts
0xffe431af…8faa
0x065c9d…c394
6 touches
3 conflicts
0x11f79447…a593
0xd32edf…ff58
5 touches
3 conflicts
0x00000000…001f
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002f
0x1b6862…e19c
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