← previous blocknext block →recent activity
Analyzing
Block #73,814,998
10 transactions · 9 stateful · 2026-05-11 04:23:21 UTC
Parallelism
70/100
Blocked
22%
Avg conflicts / tx
0.3
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #73,814,998 · 10 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w05w16w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x22e295f5…1bef
0x065c9d…c394
4 touches
1 conflict
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0x0a42f492…7385
0x065c9d…c394
2 touches
0 conflicts
0x1d32ac01…1b3f
0x065c9d…c394
2 touches
0 conflicts
0x5de96bd3…c60c
0x34b655…2a6f
2 touches
0 conflicts
0x7b97d40a…09ed
0x34b655…2a6f
2 touches
0 conflicts
0x8a85cf3d…2868
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
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity