← previous blocknext block →recent activity
Analyzing
Block #71,243,026
8 transactions · 6 stateful · 2026-04-29 06:30:47 UTC
Parallelism
75/100
Blocked
17%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #71,243,026 · 8 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x00000000…0004
0xd0f8a6…badc
4 touches
1 conflict
0x2250bf85…0c3b
0x065c9d…c394
3 touches
1 conflict
0x802ab470…5fa8
0x065c9d…c394
3 touches
1 conflict
0xb9d24e91…9fad
0x065c9d…c394
3 touches
1 conflict
0xd8d59b0c…1d0b
0x065c9d…c394
3 touches
1 conflict
0x414e9446…4b59
0x34b655…2a6f
2 touches
0 conflicts
0x53b4ef2b…8a05
0x34b655…2a6f
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: Kuru Exchange: Market-MON/USDC
1 conflict on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity