← previous blocknext block →recent activity
Analyzing
Block #72,295,903
25 transactions · 22 stateful · 2026-05-04 03:33:39 UTC
Parallelism
84/100
Blocked
55%
Avg conflicts / tx
0.8
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #72,295,903 · 25 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
1w02w13w25w06w17w08w19w011w112w013w117w119w220w321w223w224w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb9d2cf20…a668
0x34b655…2a6f
8 touches
6 conflicts
0xbb1747e2…f78b
0x34b655…2a6f
8 touches
6 conflicts
0x001e5b47…2fda
0x065c9d…c394
6 touches
3 conflicts
0x24968e6d…0132
0x065c9d…c394
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x6ed62e0d…f9dd
0xd32edf…ff58
5 touches
3 conflicts
0x01e7b865…6e6e
0x188d58…ea8e
4 touches
1 conflict
0x00000000…0012
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 0xb9d2cf2005…28a668
Audit this contract →
← previous block·next block →recent activity