← previous blocknext block →recent activity
Analyzing
Block #72,271,248
10 transactions · 10 stateful · 2026-05-04 00:48:00 UTC
Parallelism
80/100
Blocked
10%
Avg conflicts / tx
0.1
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #72,271,248 · 10 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
2w04w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8525c191…eedd
0x065c9d…c394
4 touches
1 conflict
0x9016995c…0d45
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xad7c3cf8…3ed4
0x065c9d…c394
3 touches
1 conflict
0xf64b396d…4ded
0x065c9d…c394
3 touches
1 conflict
0x4267aa17…13b9
0x065c9d…c394
3 touches
1 conflict
0xdd769895…a98d
0x065c9d…c394
3 touches
1 conflict
0x815e5dcc…819a
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 0x8525c19185…36eedd
Audit this contract →
← previous block·next block →recent activity