← previous blocknext block →recent activity
Analyzing
Block #73,596,143
23 transactions · 22 stateful · 2026-05-10 03:50:20 UTC
Parallelism
65/100
Blocked
50%
Avg conflicts / tx
1.78
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #73,596,143 · 23 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w04w17w010w112w113w215w216w317w418w519w620w721w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e295f5…1bef
0x065c9d…c394
16 touches
28 conflicts
0x046a928e…0012
0x2a68ba…90c5
14 touches
21 conflicts
0x00000000…003d
0x065c9d…c394
10 touches
10 conflicts
0x4d87512b…897c
0x065c9d…c394
6 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
0x0d622e34…0000
0x681e90…ae09
4 touches
1 conflict
0x00000000…0002
0xab3526…fa38
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
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
28 conflicts on slot 0x22e295f5d8…ac1bef
Audit this contract →
← previous block·next block →recent activity