← previous blocknext block →recent activity
Analyzing
Block #73,036,526
28 transactions · 18 stateful · 2026-05-07 13:47:38 UTC
Parallelism
86/100
Blocked
39%
Avg conflicts / tx
0.39
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #73,036,526 · 28 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w05w16w117w018w119w120w221w325w026w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0x0b390c61…dc07
0x065c9d…c394
6 touches
3 conflicts
0x56a919c4…ab49
0xee8c0e…1242
4 touches
1 conflict
0x09bbc594…9dde
0x065c9d…c394
4 touches
1 conflict
0x8a35acfb…d1ab
0x8d66a4…3095
4 touches
1 conflict
0x9d1bb389…c7d9
0x8d66a4…3095
4 touches
1 conflict
0xe89e1a22…ce49
0x8d66a4…3095
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
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity