← previous blocknext block →recent activity
Analyzing
Block #71,283,726
12 transactions · 12 stateful · 2026-04-29 11:01:41 UTC
Parallelism
83/100
Blocked
17%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #71,283,726 · 12 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
1w03w15w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdb962b83…e6be
0x065c9d…c394
4 touches
1 conflict
0x8956cb26…42fa
0x73ada1…8be0
4 touches
1 conflict
0xf3d7a307…4d63
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xb3e2c08e…5afb
0x065c9d…c394
3 touches
1 conflict
0xd8f77a40…c3d9
0x065c9d…c394
3 touches
1 conflict
0x8956cb26…42f7
0x44b60b…f711
2 touches
0 conflicts
0x8956cb26…42f9
0x44b60b…f711
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 0xdb962b830d…21e6be
Audit this contract →
← previous block·next block →recent activity