← previous blocknext block →recent activity
Analyzing
Block #71,044,391
14 transactions · 13 stateful · 2026-04-28 08:28:22 UTC
Parallelism
57/100
Blocked
46%
Avg conflicts / tx
1
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #71,044,391 · 14 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
1w04w05w16w27w39w112w413w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf3981be5…2c47
0x34b655…2a6f
10 touches
10 conflicts
0x1c389468…6b0e
0x34b655…2a6f
10 touches
10 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
8 touches
6 conflicts
0x414e9446…4b59
0x34b655…2a6f
6 touches
3 conflicts
0x4ee6f153…3ef4
0x34b655…2a6f
6 touches
3 conflicts
0x63d7ebf0…3dd9
0x34b655…2a6f
6 touches
3 conflicts
0x65e795ca…0320
0x34b655…2a6f
6 touches
3 conflicts
0x7501f58e…a219
0x34b655…2a6f
6 touches
3 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
10 conflicts on slot 0xf3981be56e…f02c47
Audit this contract →
← previous block·next block →recent activity