← previous blocknext block →recent activity
Analyzing
Block #75,014,701
16 transactions · 15 stateful · 2026-05-16 17:46:53 UTC
Parallelism
63/100
Blocked
53%
Avg conflicts / tx
1.13
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #75,014,701 · 16 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w26w07w18w29w310w411w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0008
0x509771…3c7b
12 touches
15 conflicts
0xb34209a2…164d
0x402807…5159
12 touches
15 conflicts
0x4d394876…c488
0x402807…5159
12 touches
15 conflicts
0x21c137b8…3a77
0x3bd359…433a
12 touches
15 conflicts
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x17606ba6…1b6e
0x754704…b603
4 touches
1 conflict
0x30276c1c…47b4
0x2a68ba…90c5
4 touches
1 conflict
0xc0e6d9e7…368f
0xd32edf…ff58
3 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: 0x509771f8…063c7b
15 conflicts on slot 0x0000000000…000008
Audit this contract →
← previous block·next block →recent activity