← previous blocknext block →recent activity
Analyzing
Block #71,745,719
16 transactions · 13 stateful · 2026-05-01 14:22:52 UTC
Parallelism
88/100
Blocked
15%
Avg conflicts / tx
0.19
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #71,745,719 · 16 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
2w03w011w112w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9feeec45…f4c8
0x065c9d…c394
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0xd74d5bed…5e7e
0x2a68ba…90c5
4 touches
1 conflict
0xea944055…cb1e
0x065c9d…c394
4 touches
1 conflict
0x509b73a8…f6ad
0xd32edf…ff58
3 touches
1 conflict
0xee0a9ebb…c425
0x0555e3…2b9c
2 touches
0 conflicts
0xd4d2a2e5…6be0
0x0555e3…2b9c
2 touches
0 conflicts
0x846f2172…fd54
0x0555e3…2b9c
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 0x9feeec4526…6cf4c8
Audit this contract →
← previous block·next block →recent activity