← previous blocknext block →recent activity
Analyzing
Block #71,069,927
22 transactions · 21 stateful · 2026-04-28 11:18:24 UTC
Parallelism
68/100
Blocked
48%
Avg conflicts / tx
1.05
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #71,069,927 · 22 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
5w06w19w010w111w212w013w014w315w117w218w319w420w521w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x47b807a2…3307
0x065c9d…c394
8 touches
6 conflicts
0x801a6e57…d85c
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x23114fac…630a
0x34b655…2a6f
4 touches
1 conflict
0x3254d19b…f714
0x34b655…2a6f
4 touches
1 conflict
0x3c35979a…975d
0x34b655…2a6f
4 touches
1 conflict
0x3e1f7818…2fc8
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
10 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity