← previous blocknext block →recent activity
Analyzing
Block #71,745,831
7 transactions · 6 stateful · 2026-05-01 14:23:37 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,745,831 · 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
1w03w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x78021e27…c7fd
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xb6df8f0f…52d2
0x065c9d…c394
3 touches
1 conflict
0x158828b7…941e
0x065c9d…c394
2 touches
0 conflicts
0x5f3ed433…bef2
0x065c9d…c394
2 touches
0 conflicts
0xafb02507…f83c
0x065c9d…c394
2 touches
0 conflicts
0xc4f1594e…2e70
0x065c9d…c394
2 touches
0 conflicts
0xffe431af…8faa
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 0x78021e2793…bac7fd
Audit this contract →
← previous block·next block →recent activity