← previous blocknext block →recent activity
Analyzing
Block #71,343,336
8 transactions · 7 stateful · 2026-04-29 17:38:59 UTC
Parallelism
75/100
Blocked
14%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #71,343,336 · 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
1w02w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x443a3e47…f4a4
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x3691ddd2…c20f
0x065c9d…c394
2 touches
0 conflicts
0x369fbf86…a7e4
0x065c9d…c394
2 touches
0 conflicts
0x4d4c3bf3…e6f0
0x065c9d…c394
2 touches
0 conflicts
0x5477cd93…8700
0x065c9d…c394
2 touches
0 conflicts
0x5b910f61…5d18
0x065c9d…c394
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 0x443a3e479f…3af4a4
Audit this contract →
← previous block·next block →recent activity