← previous blocknext block →recent activity
Analyzing
Block #71,289,745
20 transactions · 16 stateful · 2026-04-29 11:41:43 UTC
Parallelism
85/100
Blocked
31%
Avg conflicts / tx
0.45
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #71,289,745 · 20 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w05w19w010w112w013w114w217w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9fc6ea79…e2dc
0x34b655…2a6f
6 touches
3 conflicts
0xde38584a…ecb7
0x2a68ba…90c5
6 touches
3 conflicts
0x15a9d014…129c
0x065c9d…c394
6 touches
3 conflicts
0xcb709fe2…9ac8
0xd32edf…ff58
5 touches
3 conflicts
0x1aa94e22…82bc
0x34b655…2a6f
4 touches
1 conflict
0x1b5d2e60…99b5
0x34b655…2a6f
4 touches
1 conflict
0x23d168fb…d916
0x34b655…2a6f
4 touches
1 conflict
0x3254d19b…f714
0x34b655…2a6f
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
3 conflicts on slot 0x9fc6ea791d…ace2dc
Audit this contract →
← previous block·next block →recent activity