← previous blocknext block →recent activity
Analyzing
Block #73,696,642
34 transactions · 27 stateful · 2026-05-10 15:05:46 UTC
Parallelism
88/100
Blocked
56%
Avg conflicts / tx
0.71
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #73,696,642 · 34 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
1w02w13w24w15w26w07w111w012w013w114w215w320w122w023w124w025w126w229w030w131w232w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xab3526…fa38
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0004
0x63e48b…53f2
6 touches
3 conflicts
0xa91c899f…6ee3
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0000
0x63e48b…53f2
6 touches
3 conflicts
0xf6cc7de8…0b4a
0x3bd359…433a
6 touches
3 conflicts
0x046a928e…0012
0x2a68ba…90c5
6 touches
3 conflicts
0x00000000…0003
0x63e48b…53f2
6 touches
3 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: 0xab35264b…1cfa38
6 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity