← previous blocknext block →recent activity
Analyzing
Block #73,036,066
8 transactions · 7 stateful · 2026-05-07 13:44:33 UTC
Parallelism
75/100
Blocked
14%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #73,036,066 · 8 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
1w03w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x81e39bf1…ee84
0x065c9d…c394
4 touches
1 conflict
0x65fe19d9…627f
0x065c9d…c394
3 touches
1 conflict
0x7d8b5c38…4303
0x065c9d…c394
3 touches
1 conflict
0x2ebf2fcb…491f
0x065c9d…c394
2 touches
0 conflicts
0x5171dfc5…9afc
0x065c9d…c394
2 touches
0 conflicts
0x59f89984…f48b
0x065c9d…c394
2 touches
0 conflicts
0x6ac9faaf…89f9
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 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity