← previous blocknext block →recent activity
Analyzing
Block #71,043,039
12 transactions · 11 stateful · 2026-04-28 08:19:21 UTC
Parallelism
75/100
Blocked
27%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #71,043,039 · 12 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
2w06w08w110w111w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1c389468…6b0e
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0004
0xd0f8a6…badc
4 touches
1 conflict
0x8f2d4996…a83c
0x065c9d…c394
3 touches
1 conflict
0xfd6983f8…188c
0x065c9d…c394
3 touches
1 conflict
0x65ed8c13…0446
0x065c9d…c394
3 touches
1 conflict
0xe0a6ac64…9b31
0x065c9d…c394
3 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 0x1c38946843…a16b0e
Audit this contract →
← previous block·next block →recent activity