← previous blocknext block →recent activity
Analyzing
Block #75,014,353
18 transactions · 17 stateful · 2026-05-16 17:44:31 UTC
Parallelism
72/100
Blocked
53%
Avg conflicts / tx
1
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #75,014,353 · 18 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w06w07w18w29w310w414w115w216w317w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0008
0x509771…3c7b
10 touches
10 conflicts
0xb34209a2…164d
0x402807…5159
10 touches
10 conflicts
0x4d394876…c488
0x402807…5159
10 touches
10 conflicts
0x21c137b8…3a77
0x3bd359…433a
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0x388f889f…a655
0x34b655…2a6f
6 touches
3 conflicts
0x3e49348b…9445
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: 0x509771f8…063c7b
10 conflicts on slot 0x0000000000…000008
Audit this contract →
← previous block·next block →recent activity