← previous blocknext block →recent activity
Analyzing
Block #71,559,411
9 transactions · 8 stateful · 2026-04-30 17:42:38 UTC
Parallelism
78/100
Blocked
13%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #71,559,411 · 9 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
5w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfcb7b8b2…ebb3
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x3c30b651…cf8c
0x065c9d…c394
3 touches
1 conflict
0x9e3ab74f…a26a
0x065c9d…c394
3 touches
1 conflict
0xce51d93c…2846
0x065c9d…c394
3 touches
1 conflict
0x8c015090…cfd5
0x065c9d…c394
2 touches
0 conflicts
0x6b000777…7040
0x2a68ba…90c5
2 touches
0 conflicts
0x9f52c733…da60
0x67d1be…196f
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 0xfcb7b8b239…6bebb3
Audit this contract →
← previous block·next block →recent activity