← previous blocknext block →recent activity
Analyzing
Block #73,215,827
10 transactions · 9 stateful · 2026-05-08 09:40:35 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,215,827 · 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
5w06w17w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x046a928e…0012
0x2a68ba…90c5
6 touches
3 conflicts
0xbd7e37a9…9eb5
0x065c9d…c394
6 touches
3 conflicts
0x43f02fe0…f464
0x1b6862…e19c
2 touches
0 conflicts
0x6be7b977…23d2
0x57ea24…2cec
2 touches
0 conflicts
0xacbbafe4…c836
0x57ea24…2cec
2 touches
0 conflicts
0x00000000…0004
0x5e0734…69c1
2 touches
0 conflicts
0x525698e3…bcc8
0x5e0734…69c1
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