← previous blocknext block →recent activity
Analyzing
Block #71,043,349
13 transactions · 13 stateful · 2026-04-28 08:21:25 UTC
Parallelism
77/100
Blocked
23%
Avg conflicts / tx
0.31
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #71,043,349 · 13 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
4w08w09w111w112w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1c389468…6b0e
0x34b655…2a6f
6 touches
3 conflicts
0x5c8c6ab6…dc36
0x131a2e…0da9
4 touches
1 conflict
0x63d7ebf0…3dd9
0x34b655…2a6f
4 touches
1 conflict
0xc64798fd…7528
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x4ab14837…e1b2
0x2a68ba…90c5
4 touches
1 conflict
0x0520da1d…c88e
0x34b655…2a6f
2 touches
0 conflicts
0x6af306bb…2e81
0x3bd359…433a
2 touches
0 conflicts
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 0x1c38946843…a16b0e
Audit this contract →
← previous block·next block →recent activity