← previous blocknext block →recent activity
Analyzing
Block #71,042,802
13 transactions · 12 stateful · 2026-04-28 08:17:45 UTC
Parallelism
85/100
Blocked
8%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #71,042,802 · 13 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
4w05w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3625ca65…6f73
0x065c9d…c394
4 touches
1 conflict
0x51ecdf19…e365
0x065c9d…c394
4 touches
1 conflict
0x66a51112…6aa3
0x065c9d…c394
4 touches
1 conflict
0xd307e808…bc34
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x00000000…0004
0xd0f8a6…badc
4 touches
1 conflict
0x1c389468…6b0e
0x34b655…2a6f
2 touches
0 conflicts
0x3c35979a…975d
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 0x3625ca65f1…c36f73
Audit this contract →
← previous block·next block →recent activity