← previous blocknext block →recent activity
Analyzing
Block #73,991,739
12 transactions · 10 stateful · 2026-05-12 00:01:48 UTC
Parallelism
58/100
Blocked
50%
Avg conflicts / tx
0.92
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #73,991,739 · 12 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w16w27w28w39w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
10 touches
10 conflicts
0x6f08361d…bda6
0x065c9d…c394
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x98103e5c…f3f5
0x065c9d…c394
4 touches
1 conflict
0x05eea3e3…5846
0x2a68ba…90c5
4 touches
1 conflict
0x34835b11…5888
0x065c9d…c394
3 touches
1 conflict
0xfa2541d9…f207
0x065c9d…c394
3 touches
1 conflict
0xd43ef8b2…0d15
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
10 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity