← previous blocknext block →recent activity
Analyzing
Block #73,216,548
9 transactions · 9 stateful · 2026-05-08 09:45:23 UTC
Parallelism
78/100
Blocked
11%
Avg conflicts / tx
0.22
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #73,216,548 · 9 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
1w03w05w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x35de08be…b167
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x28cdd480…a2b1
0x065c9d…c394
3 touches
1 conflict
0x0b68c03a…009a
0x065c9d…c394
2 touches
0 conflicts
0x63d7b3f1…de55
0x065c9d…c394
2 touches
0 conflicts
0x8e2c5a14…00fd
0x065c9d…c394
2 touches
0 conflicts
0xbd7e37a9…9eb5
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 0x35de08bedf…c1b167
Audit this contract →
← previous block·next block →recent activity