← previous blocknext block →recent activity
Analyzing
Block #71,042,900
8 transactions · 8 stateful · 2026-04-28 08:18:25 UTC
Parallelism
63/100
Blocked
25%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #71,042,900 · 8 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
4w05w17w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x56db71ea…e911
0x065c9d…c394
4 touches
3 conflicts
0x96840480…1165
0x065c9d…c394
4 touches
1 conflict
0xb736518f…f246
0x065c9d…c394
4 touches
1 conflict
0xeb1792fb…ff13
0x065c9d…c394
4 touches
1 conflict
0xf8041dd1…50d4
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x5ab9ba62…578a
0x065c9d…c394
4 touches
1 conflict
0x00000000…0004
0xd0f8a6…badc
4 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: Kuru Exchange: Market-MON/USDC
3 conflicts on slot 0x56db71ea3d…91e911
Audit this contract →
← previous block·next block →recent activity