← previous blocknext block →recent activity
Analyzing
Block #71,342,939
7 transactions · 6 stateful · 2026-04-29 17:36:20 UTC
Parallelism
71/100
Blocked
17%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #71,342,939 · 7 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
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x4ec93cff…9db9
0x065c9d…c394
2 touches
0 conflicts
0x5a1553e2…e9ea
0x065c9d…c394
2 touches
0 conflicts
0x76312195…8c2b
0x065c9d…c394
2 touches
0 conflicts
0x8f467a46…7b4c
0x065c9d…c394
2 touches
0 conflicts
0xa6dbb1a1…da8f
0x065c9d…c394
2 touches
0 conflicts
0xb16be010…42de
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 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity