← previous blocknext block →recent activity
Analyzing
Block #71,445,613
7 transactions · 7 stateful · 2026-04-30 05:00:46 UTC
Parallelism
71/100
Blocked
29%
Avg conflicts / tx
0.29
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #71,445,613 · 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
2w03w04w16w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9b24f724…af14
0x065c9d…c394
4 touches
1 conflict
0x451e482b…7e7d
0x34b655…2a6f
4 touches
1 conflict
0x7cd8b4be…886d
0x065c9d…c394
3 touches
1 conflict
0x65cb81f2…f4ce
0x065c9d…c394
3 touches
1 conflict
0x00000000…0004
0x5afd3e…7620
2 touches
0 conflicts
0x1fd61957…8889
0x5afd3e…7620
2 touches
0 conflicts
0xf49c065b…e408
0x5afd3e…7620
2 touches
0 conflicts
0x00000000…0006
0x60bb42…87ea
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 0x9b24f7242f…29af14
Audit this contract →
← previous block·next block →recent activity