← previous blocknext block →recent activity
Analyzing
Block #72,172,890
11 transactions · 11 stateful · 2026-05-03 13:47:02 UTC
Parallelism
82/100
Blocked
9%
Avg conflicts / tx
0.09
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #72,172,890 · 11 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
0x13f2150f…ef62
0x065c9d…c394
4 touches
1 conflict
0x97890320…c958
0x065c9d…c394
3 touches
1 conflict
0x6cd70afa…8790
0x065c9d…c394
3 touches
1 conflict
0x0520da1d…c88e
0x34b655…2a6f
2 touches
0 conflicts
0x17e2d2a0…359e
0x34b655…2a6f
2 touches
0 conflicts
0x1b5d2e60…99b5
0x34b655…2a6f
2 touches
0 conflicts
0x1c389468…6b0e
0x34b655…2a6f
2 touches
0 conflicts
0x2877f440…c2c8
0x34b655…2a6f
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 0x13f2150fc5…48ef62
Audit this contract →
← previous block·next block →recent activity