← previous blocknext block →recent activity
Analyzing
Block #71,042,911
5 transactions · 5 stateful · 2026-04-28 08:18:29 UTC
Parallelism
60/100
Blocked
20%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #71,042,911 · 5 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
1w02w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x11f8cd5b…5bdf
0x065c9d…c394
4 touches
1 conflict
0x191bddf4…de78
0x065c9d…c394
4 touches
1 conflict
0x748f0446…0a1d
0x065c9d…c394
4 touches
1 conflict
0x8f2d4996…a83c
0x065c9d…c394
4 touches
1 conflict
0xc95b55c4…10b7
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x00000000…0004
0xd0f8a6…badc
4 touches
1 conflict
0xf7e61d9c…aea1
0x065c9d…c394
2 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
1 conflict on slot 0x11f8cd5b20…b95bdf
Audit this contract →
← previous block·next block →recent activity