← previous blocknext block →recent activity
Analyzing
Block #73,437,925
8 transactions · 8 stateful · 2026-05-09 10:18:16 UTC
Parallelism
75/100
Blocked
13%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #73,437,925 · 8 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
1w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e295f5…1bef
0x065c9d…c394
4 touches
1 conflict
0xab677e99…b3b8
0x065c9d…c394
3 touches
1 conflict
0x1c317ad0…a3f0
0x065c9d…c394
3 touches
1 conflict
0x03987294…d70a
0x065c9d…c394
2 touches
0 conflicts
0x2efe4d35…3f1b
0x065c9d…c394
2 touches
0 conflicts
0x4d87512b…897c
0x065c9d…c394
2 touches
0 conflicts
0xf7bde180…b009
0x065c9d…c394
2 touches
0 conflicts
0xae69c125…2379
0x2a68ba…90c5
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 0x22e295f5d8…ac1bef
Audit this contract →
← previous block·next block →recent activity