← previous blocknext block →recent activity
Analyzing
Block #71,423,008
21 transactions · 19 stateful · 2026-04-30 02:30:08 UTC
Parallelism
67/100
Blocked
63%
Avg conflicts / tx
1.05
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #71,423,008 · 21 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w26w07w18w210w011w012w113w114w215w117w318w419w520w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1c913164…5c2e
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x892daf6e…48d8
0x065c9d…c394
6 touches
3 conflicts
0x49f231bb…c1c2
0x34b655…2a6f
6 touches
3 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
6 touches
3 conflicts
0x6737ee07…9978
0x34b655…2a6f
6 touches
3 conflicts
0x7170c140…36bc
0x34b655…2a6f
6 touches
3 conflicts
0x947b3296…e75f
0x34b655…2a6f
6 touches
3 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 0x1c913164f5…845c2e
Audit this contract →
← previous block·next block →recent activity