← previous blocknext block →recent activity
Analyzing
Block #72,166,858
7 transactions · 5 stateful · 2026-05-03 13:06:31 UTC
Parallelism
71/100
Blocked
20%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #72,166,858 · 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
1w04w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x18c8e7c1…8d0c
0x065c9d…c394
2 touches
0 conflicts
0x3ad1e24e…de94
0x065c9d…c394
2 touches
0 conflicts
0xd5a7018a…f881
0x065c9d…c394
2 touches
0 conflicts
0xfe70488d…a9e8
0x065c9d…c394
2 touches
0 conflicts
0xbf04f37d…85f2
0x2a68ba…90c5
2 touches
0 conflicts
0x109d8a52…a7b7
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 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity