← previous blocknext block →recent activity
Analyzing
Block #72,227,988
4 transactions · 3 stateful · 2026-05-03 19:57:12 UTC
Parallelism
50/100
Blocked
33%
Avg conflicts / tx
0.25
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #72,227,988 · 4 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
1w02w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfd0aafcc…9918
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x77eb0d8c…61db
0x065c9d…c394
3 touches
1 conflict
0x447b3ca6…389a
0x065c9d…c394
3 touches
1 conflict
0x58fbe430…3b44
0x065c9d…c394
2 touches
0 conflicts
0xac5fb230…ef0e
0x065c9d…c394
2 touches
0 conflicts
0xaead6ee6…0058
0x065c9d…c394
2 touches
0 conflicts
0xf8756adb…f761
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 0xfd0aafcc3d…b09918
Audit this contract →
← previous block·next block →recent activity