← previous blocknext block →recent activity
Analyzing
Block #73,697,076
16 transactions · 12 stateful · 2026-05-10 15:08:43 UTC
Parallelism
75/100
Blocked
33%
Avg conflicts / tx
0.44
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #73,697,076 · 16 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
1w02w03w17w110w211w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0x0ac31945…2c72
0x065c9d…c394
4 touches
1 conflict
0xf0f673fd…37a7
0x6c4bfa…a540
4 touches
1 conflict
0x2e2214a9…fe0d
0x6c4bfa…a540
4 touches
1 conflict
0xae69c125…2379
0x2a68ba…90c5
4 touches
1 conflict
0xed57bddf…1abf
0xc8689a…ee79
4 touches
1 conflict
0x529acb6a…fcc6
0x065c9d…c394
4 touches
1 conflict
0x00000000…0002
0xab3526…fa38
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
6 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity