← previous blocknext block →recent activity
Analyzing
Block #72,309,408
58 transactions · 38 stateful · 2026-05-04 05:03:39 UTC
Parallelism
86/100
Blocked
71%
Avg conflicts / tx
1.31
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #72,309,408 · 58 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w69w214w128w533w238w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7b7bcac3…8fbf
0x34b655…2a6f
14 touches
21 conflicts
0xb44f41c4…8c24
0xd32edf…ff58
13 touches
21 conflicts
0xea02471d…1542
0x34b655…2a6f
12 touches
15 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0xe5e7089a…fb91
0x34b655…2a6f
8 touches
6 conflicts
0xf3d10975…0d07
0x34b655…2a6f
8 touches
6 conflicts
0xf6cc7de8…0b4a
0x3bd359…433a
8 touches
6 conflicts
0x00000000…0000
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
21 conflicts on slot 0x7b7bcac3fe…968fbf
Audit this contract →
← previous block·next block →recent activity