← previous blocknext block →recent activity
Analyzing
Block #73,273,464
19 transactions · 15 stateful · 2026-05-08 16:04:01 UTC
Parallelism
79/100
Blocked
47%
Avg conflicts / tx
0.74
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #73,273,464 · 19 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
1w02w15w06w18w210w311w012w213w317w018w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0x00000000…0002
0xab3526…fa38
8 touches
6 conflicts
0xda4736d0…000f
0x065c9d…c394
6 touches
3 conflicts
0x10cde0ad…15df
0x065c9d…c394
5 touches
3 conflicts
0xd761c2b8…121b
0x065c9d…c394
4 touches
1 conflict
0x2d5e75ab…5b6d
0x34b655…2a6f
4 touches
1 conflict
0x47c1a8e8…f74a
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
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