← previous blocknext block →recent activity
Analyzing
Block #71,283,727
18 transactions · 18 stateful · 2026-04-29 11:01:42 UTC
Parallelism
83/100
Blocked
39%
Avg conflicts / tx
0.56
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #71,283,727 · 18 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
1w02w13w26w07w19w010w011w112w215w116w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xb857c1…9be1
6 touches
3 conflicts
0x6ea8fa8d…3dd8
0x1b6862…e19c
6 touches
3 conflicts
0x77905798…fe3d
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x7714df01…3e5d
0xd32edf…ff58
5 touches
3 conflicts
0x22e0cc1d…ad04
0x34b655…2a6f
4 touches
1 conflict
0xe54a1f6f…18f2
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: 0xb857c13a…1a9be1
3 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity