← previous blocknext block →recent activity
Analyzing
Block #73,749,175
57 transactions · 45 stateful · 2026-05-10 21:00:22 UTC
Parallelism
74/100
Blocked
73%
Avg conflicts / tx
2.81
Longest chain
15 deep
Execution timeline
did this block parallelize well?
view
block #73,749,175 · 57 txs across 15 waves · depth 15
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w07w08w19w210w311w412w513w615w716w817w918w1019w1120w1221w1322w1440w141w242w143w244w345w446w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xab3526…fa38
30 touches
105 conflicts
0x15d039e7…4bb6
0x34b655…2a6f
12 touches
15 conflicts
0x00000000…003d
0x065c9d…c394
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
10 touches
10 conflicts
0x7f81fb82…633e
0x065c9d…c394
8 touches
6 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
8 touches
6 conflicts
0x057de4f5…df60
0x34b655…2a6f
8 touches
6 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
105 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity