← previous blocknext block →recent activity
Analyzing
Block #73,216,694
14 transactions · 11 stateful · 2026-05-08 09:46:21 UTC
Parallelism
86/100
Blocked
18%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #73,216,694 · 14 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
4w05w06w113w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xdaca243a…f9de
0x34b655…2a6f
4 touches
1 conflict
0x0cc114a8…4364
0x065c9d…c394
4 touches
1 conflict
0x21c699e2…3e64
0x065c9d…c394
3 touches
1 conflict
0x4ecc9b73…cd99
0x065c9d…c394
3 touches
1 conflict
0xb7c5591b…8860
0x065c9d…c394
2 touches
0 conflicts
0xc6e4a6bd…e2b6
0x065c9d…c394
2 touches
0 conflicts
0x0eac6378…36f4
0x34b655…2a6f
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 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity