← previous blocknext block →recent activity
Analyzing
Block #72,287,869
35 transactions · 30 stateful · 2026-05-04 02:39:45 UTC
Parallelism
86/100
Blocked
63%
Avg conflicts / tx
0.97
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #72,287,869 · 35 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w15w16w27w08w111w212w313w217w018w119w224w325w226w327w328w229w434w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60f7fbaf…bd58
0x34b655…2a6f
8 touches
6 conflicts
0xa92c8763…6d7f
0x34b655…2a6f
8 touches
6 conflicts
0xbb1747e2…f78b
0x34b655…2a6f
8 touches
6 conflicts
0xf3808e5a…dbfb
0x34b655…2a6f
8 touches
6 conflicts
0xf6cc7de8…0b4a
0x3bd359…433a
8 touches
6 conflicts
0x00000000…0000
0x63e48b…53f2
8 touches
6 conflicts
0x00000000…0003
0x63e48b…53f2
8 touches
6 conflicts
0x00000000…0004
0x63e48b…53f2
8 touches
6 conflicts
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