← previous blocknext block →recent activity
Analyzing
Block #71,329,258
24 transactions · 23 stateful · 2026-04-29 16:05:03 UTC
Parallelism
75/100
Blocked
48%
Avg conflicts / tx
0.88
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #71,329,258 · 24 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w17w08w112w213w214w316w417w519w220w321w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x631b4113…baa9
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0xba38536d…2b7d
0x065c9d…c394
8 touches
6 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0x348fda08…7e96
0x065c9d…c394
6 touches
3 conflicts
0x15c9b5bf…f732
0x34b655…2a6f
6 touches
3 conflicts
0x26a96f1d…523f
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…002d
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 0x631b41138f…31baa9
Audit this contract →
← previous block·next block →recent activity